Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > DPA 11.1 feature: Improved monitoring of SQL Server Availability Groups

DPA 11.1 feature: Improved monitoring of SQL Server Availability Groups

Updated October 16th, 2017


DPA provides the following information about SQL Server Availability Groups (AGs):

AG information on the DPA Home page


The AG Status Summary box in the Status Summary area shows the number of database instances with partially healthy or unhealthy AGs. As with other status boxes, click the filter next to a status to display only instances with that status.

If you register the AG via the listener, the DPA displays the instance name as "PrimaryReplicaName via ListenerName" (as shown in the figure above). When a failover occurs, the name is automatically updated to reflect the new primary replica.

If you manually change the display name of an AG that is registered via the listener, by default DPA overwrites the name each time the monitor starts. To change the default behavior and manually specify the name, change the advanced option AG_INSTANCE_NAME_UPDATE_ENABLED.

The AG status icon AG_status_icons.png identifies database instances that include AGs. The color of the dot indicates the AG status: 

  • Green for healthy
  • Yellow for partially healthy
  • Red for unhealthy
  • Gray for unknown

To determine the AG status:

  • If you are monitoring the instance directly (not through a listener), DPA displays the worst status of any AG that the instance is the primary replica for. It ignores the status of an AG if that AG is a secondary replica.

    Example: An instance is the primary replica for four availability groups. Their statuses are Healthy, Healthy, Partially Healthy, and Not Healthy. DPA shows the status as Not Healthy.

  • If you are monitoring the instance via the listener, by default DPA displays the aggregate status as described above. However, you can use the advanced system option AG_STATUS_ROLLUP_USE_PRIMARY to determine the status using only the AG associated with the listener.

Availability Group Summary

From the DPA Home page, click an AG status icon to open the Availability Group Summary view, which shows information about each AG in the database instance. DPA shows status information for primary replicas in the instance. For secondary replicas, the status of the primary replica is displayed if DPA is also monitoring the primary replica. 


Click any link to view more detailed information about the databases and replicas in the AG.

Automatic annotations when AG failovers occur

Annotations are automatically added to wait time charts when an AG failover occurs. The annotations allow you to compare changes in performance before and after a failover.

If you do not want to add an annotation when an AG failover occurs, change the value of the advanced system option AG_EVENT_ANNOTATIONS_ENABLED.

AG alerts

You can configure DPA to alert you when:

  • An AG status changes to Partially Healthy or Not Healthy
  • An AG failover occurs

When you configure the SQL Server Availability Group Status Change alert, DPA evaluates AG statuses every 10 minutes by default. You are alerted if the status changes from Healthy to Partially Healthy or Not Healthy between the evaluations. If the status changes from Healthy to another status and then back to Healthy during the same evaluation period, you are not alerted. 

When you configure the SQL Server Availability Group Failover alert, DPA sends alerts based on how you registered instances:

  • If you registered database instances directly (not through a listener), when a failover occurs DPA sends an alert for each instance involved in the failover that it is monitoring. For example, if an AG fails over from Instance1 to Instance2 and DPA is monitoring both instances, you will receive two alerts. If DPA is monitoring only one of the instances, you will receive only one alert.
  • If you registered the AG through a listener and the AG associated with the listener fails over, DPA sends one alert, because the listener moves with the AG from Instance1 to Instance2. 

If multiple AG failovers occur, DPA aggregates them into one alert per instance.

Last modified