search cancel

sqlserver probe no longer alarming for AlwaysOn metrics, and or collecting those metrics

book

Article ID: 240968

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We had a series of servers that were collecting AlwaysOn metrics and alarming and it seems that they are not longer reporting or alarming for these metrics

Cause

Superpack was pushed that contained connection updates that turned the metrics off.

Environment

Release : 20.4

Component : UIM - SQLSERVER

Resolution

-turn off AlwaysOn on that connection and save (no longer got the metrics in status) 
-turn on AlwaysOn for that connection and save (the metrics came back in status)

Alternatively in those places where a .cfg was pushed out that had:

is_AlwaysOn = 

or

is_AlwaysOn = 0

and the metrics where being polled initially, than just changing this to:

is_AlwaysOn = 1

and restarting the probe should bring the metrics.

Also clicking Test for the connection in IM or AC should bring the metrics back as well.

Additional Information

When turning on AlwaysOn on in the connection configuration UI, the probe will check to validate that AlwaysOn is active on the machine, and then will update the is_AlwaysOn value in the sqlserver.cfg file. If AlwaysOn is found to be running on the SQL server than this value will change to 1.

Also see the following for more details on AlwaysOn metric collection requirements:

https://knowledge.broadcom.com/external/article?articleId=130138