cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MSSQL Always-On Availability Group

Osama.Abbas
Producer

Hi community,

I have an AO AG with two nodes, and I have these four IP addresses.

10.10.10.62 (DB 1)
10.10.10.63 (DB 2)
10.10.10.61 (Cluster IP)
10.10.10.60 (AG Listener IP)

I want to discover the two nodes automatically. According to the documentation, Configure Microsoft SQL Server Collectors (appdynamics.com)

To enable monitoring of all the nodes, you must enable the dbagent.mssql.cluster.discovery.enabled property either at the Controller level or at the agent level.

I am running the following:

$ nohup java -Dappdynamics.agent.maxMetrics=300000 -Ddbagent.name=DBMon-Agent -jar db-agent.jar -Ddbagent.mssql.cluster.discovery.enabled=true &

But it doesn't work when I configure the collector with the AG Listener IP.

I also get the below: `Is Failover Cluster Discovery Enabled: False`! I have added dbagent.mssql.cluster.discovery.enabled though!?

Is Fail Over cluster enabled.png

What could I possibly be doing wrong?

Thank you

6 REPLIES 6

Ryan.Paredez
Community Manager

Hi @Osama.Abbas 

I noticed the Community has not yet jumped in to help. Did you happen to make any discoveries or find a solution you could share?


Thanks,

Ryan, Cisco AppDynamics Community Manager




Found something helpful? Click the Accept as Solution button to help others find answers faster.

Liked something? Click the Thumbs Up button.



Check out Observabiity in Action

new deep dive videos weekly in the Knowledge Base.

Hi @Ryan.Paredez ,

Unfortunately, I have not found any resolution for my issue just yet and it is not clear in the documentation how to use:

dbagent.mssql.cluster.discovery.enabled

from the Controller UI.

 Thank  you,

Osama

Ryan.Paredez
Community Manager

Hi @Osama.Abbas,

I have shared your feedback with the Docs team. I will report back when I hear from them. 


Thanks,

Ryan, Cisco AppDynamics Community Manager




Found something helpful? Click the Accept as Solution button to help others find answers faster.

Liked something? Click the Thumbs Up button.



Check out Observabiity in Action

new deep dive videos weekly in the Knowledge Base.

Ryan.Paredez
Community Manager

Hi @Osama.Abbas,

I'm still waiting to hear back from the Docs team. Have you found a solution you could share in the meantime?


Thanks,

Ryan, Cisco AppDynamics Community Manager




Found something helpful? Click the Accept as Solution button to help others find answers faster.

Liked something? Click the Thumbs Up button.



Check out Observabiity in Action

new deep dive videos weekly in the Knowledge Base.

Hi @Ryan.Paredez 

Thanks a lot for following up with my question. I really appreciate it.

Unfortunately, I was not able to solve it on my own till now and I had to discover just the primary node as a workaround until I can find a solution to my problem.

Thanks once again

Ryan.Paredez
Community Manager

Hi @Osama.Abbas,

Thanks for letting me know. I'm still working with the Docs team to see if we can get any information on that Docs page clarified. 


Thanks,

Ryan, Cisco AppDynamics Community Manager




Found something helpful? Click the Accept as Solution button to help others find answers faster.

Liked something? Click the Thumbs Up button.



Check out Observabiity in Action

new deep dive videos weekly in the Knowledge Base.

June 26 Webinar
Discover new Splunk integrations and AI innovations for Cisco AppDynamics.


Register Now!

Observe and Explore
Dive into our Community Blog for the Latest Insights and Updates!


Read the blog here