How to add/monitor SQL Availability Groups

I am starting down a bit of a rabbit hole here and wanted to get input.

How do you properly monitor a SQL AG? Do we need to add the AG Listener and use that or should we just monitor the nodes separately? If I go into my Orion console I will see SQLNODE1, SQLNODE2, SQLNODE02 but one of the 02 nodes is the AG and one of the 02 nodes is the actual SQL Node.

Find more posts tagged with

sql

Accepted answers

All comments

tobyw_loop1

I have the same problem. and it's a little big vague when looking at documentation for NPM as opposed to DPA or SQL Sentry.

martian_monster

So I ended up creating a custom SAM application based upon the Windows Failover Cluster services. While it is not exactly what I was looking for it works for the DBA team and our Patching team to ID if there are issues. So it is not exactly monitoring a SQL AG but it gives us the visibility that we need.

tobyw_loop1

Feel free to share to the contact exchange here, if it's not already there! The only concise thread I could find on here otherwise was this one https://thwack.solarwinds.com/product-forums/server-application-monitor-sam/f/forum/57308/appinsight-for-sql-always-on-cluster-monitoring

That leads to monitoring in the following manner

AppInsight for SQL on the ClusterIP
'Standard' SNMP/WMI monitoring on the cluster nodes.