<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: MSSQL Always-On Availability Group in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/720573#M2092</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;A href="https://community.appdynamics.com/t5/user/viewprofilepage/user-id/168025"&gt;@Osama.Abbas&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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?&lt;/P&gt;</description>
    <pubDate>Fri, 08 Mar 2024 18:30:08 GMT</pubDate>
    <dc:creator>iamryan</dc:creator>
    <dc:date>2024-03-08T18:30:08Z</dc:date>
    <item>
      <title>MSSQL Always-On Availability Group</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/720572#M2091</link>
      <description>&lt;P&gt;Hi community,&lt;/P&gt;&lt;P&gt;I have an AO AG with two nodes, and I have these four IP addresses.&lt;/P&gt;&lt;PRE class="lia-code-sample language-markup"&gt;&lt;CODE&gt;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)&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;I want to discover the two nodes automatically. According to the documentation,&amp;nbsp;&lt;A href="https://docs.appdynamics.com/appd/21.x/21.12/en/database-visibility/add-database-collectors/configure-microsoft-sql-server-collectors#id-.ConfigureMicrosoftSQLServerCollectorsv21.11-MonitortheMicrosoftSQLServerClustermonitor-mssql-server-cluster" target="_blank" rel="nofollow noopener noreferrer"&gt;Configure Microsoft SQL Server Collectors (appdynamics.com)&lt;/A&gt;&lt;/P&gt;&lt;PRE class="lia-code-sample language-markup"&gt;&lt;CODE&gt;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.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;I am running the following:&lt;/P&gt;&lt;PRE class="lia-code-sample language-python"&gt;&lt;CODE&gt;$ nohup java -Dappdynamics.agent.maxMetrics=300000 -Ddbagent.name=DBMon-Agent -jar db-agent.jar -Ddbagent.mssql.cluster.discovery.enabled=true &amp;amp;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;But it doesn't work when I configure the collector with the AG Listener IP.&lt;/P&gt;&lt;P&gt;I also get the below: `Is Failover Cluster Discovery Enabled: False`! I have added&amp;nbsp;&lt;SPAN&gt;dbagent.mssql.cluster.discovery.enabled though!?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="Is Fail Over cluster enabled.png" style="width: 999px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="image.png"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/35564iB443DE1F037D3C04/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;What could I possibly be doing wrong?&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 17:49:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/720572#M2091</guid>
      <dc:creator>Osama_Abbas</dc:creator>
      <dc:date>2024-03-06T17:49:07Z</dc:date>
    </item>
    <item>
      <title>Re: MSSQL Always-On Availability Group</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/720573#M2092</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;A href="https://community.appdynamics.com/t5/user/viewprofilepage/user-id/168025"&gt;@Osama.Abbas&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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?&lt;/P&gt;</description>
      <pubDate>Fri, 08 Mar 2024 18:30:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/720573#M2092</guid>
      <dc:creator>iamryan</dc:creator>
      <dc:date>2024-03-08T18:30:08Z</dc:date>
    </item>
    <item>
      <title>Re: MSSQL Always-On Availability Group</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/720574#M2093</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;A href="https://community.appdynamics.com/t5/user/viewprofilepage/user-id/142051"&gt;@Ryan.Paredez&lt;/A&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Unfortunately, I have not found any resolution for my issue just yet and it is not clear in the documentation how to use:&lt;/P&gt;&lt;PRE class="lia-code-sample language-markup"&gt;&lt;CODE&gt;dbagent.mssql.cluster.discovery.enabled&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;from the Controller UI.&lt;/P&gt;&lt;P&gt;&amp;nbsp;Thank&amp;nbsp; you,&lt;/P&gt;&lt;P&gt;Osama&lt;/P&gt;</description>
      <pubDate>Sat, 09 Mar 2024 09:55:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/720574#M2093</guid>
      <dc:creator>Osama_Abbas</dc:creator>
      <dc:date>2024-03-09T09:55:47Z</dc:date>
    </item>
    <item>
      <title>Re: MSSQL Always-On Availability Group</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/720575#M2094</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;A href="https://community.appdynamics.com/t5/user/viewprofilepage/user-id/168025"&gt;@Osama.Abbas&lt;/A&gt;,&lt;/P&gt;
&lt;P&gt;I have shared your feedback with the Docs team. I will report back when I hear from them.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2024 17:30:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/720575#M2094</guid>
      <dc:creator>iamryan</dc:creator>
      <dc:date>2024-03-11T17:30:45Z</dc:date>
    </item>
    <item>
      <title>Re: MSSQL Always-On Availability Group</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/720576#M2095</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;A href="https://community.appdynamics.com/t5/user/viewprofilepage/user-id/168025"&gt;@Osama.Abbas&lt;/A&gt;,&lt;/P&gt;
&lt;P&gt;I'm still waiting to hear back from the Docs team. Have you found a solution you could share in the meantime?&lt;/P&gt;</description>
      <pubDate>Thu, 21 Mar 2024 16:18:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/720576#M2095</guid>
      <dc:creator>iamryan</dc:creator>
      <dc:date>2024-03-21T16:18:45Z</dc:date>
    </item>
    <item>
      <title>Re: MSSQL Always-On Availability Group</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/720577#M2096</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;A href="https://community.appdynamics.com/t5/user/viewprofilepage/user-id/142051"&gt;@Ryan.Paredez&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks a lot for following up with my question. I really appreciate it.&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;Thanks once again&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2024 20:34:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/720577#M2096</guid>
      <dc:creator>Osama_Abbas</dc:creator>
      <dc:date>2024-03-26T20:34:03Z</dc:date>
    </item>
    <item>
      <title>Re: MSSQL Always-On Availability Group</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/720578#M2097</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;A href="https://community.appdynamics.com/t5/user/viewprofilepage/user-id/168025"&gt;@Osama.Abbas&lt;/A&gt;,&lt;/P&gt;
&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2024 16:01:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/720578#M2097</guid>
      <dc:creator>iamryan</dc:creator>
      <dc:date>2024-03-27T16:01:53Z</dc:date>
    </item>
    <item>
      <title>Re: MSSQL Always-On Availability Group</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/751748#M11947</link>
      <description>&lt;P&gt;Hola!&lt;/P&gt;&lt;P&gt;puedes intentar con:&lt;/P&gt;&lt;P&gt;-Ddbagent.mssql.cluster.discovery="true"&lt;/P&gt;&lt;P&gt;en el archivo de configuración:&lt;/P&gt;&lt;P&gt;\bin\DatabaseAgentService.vmoptions&lt;/P&gt;&lt;P&gt;(Si no existe este archivo, puedes crearlo)&lt;/P&gt;&lt;P&gt;Y me comentas si te funciona, Saludos!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 16 Aug 2025 06:55:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/MSSQL-Always-On-Availability-Group/m-p/751748#M11947</guid>
      <dc:creator>Ricardo_Guzman</dc:creator>
      <dc:date>2025-08-16T06:55:30Z</dc:date>
    </item>
  </channel>
</rss>

