The alarm variable for a custom checkpoint in the sqlserver probe is not working properly

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

The steps to configure a custom checkpoint for the sqlserver probe were followed in the article "How to create a new (custom) checkpoint using the sqlserver probe" but the alarm variable is not working properly.

 

For example, in the query below, the alarm needs to be trigger based on the SQL server 'current count' alias, but alarm the variable is not working properly

 

select count(*) as 'current count' from CA_UIM.dbo.SSRV2AuditTrail

 

Threshold/Schedules is configured as followed with Message Text: Profile $profile, checkpoint '$check' value is greater than 1000. Current count is $current count

 

 

Alarm is generated but note that the 'current count' does not have the expected value

 

Environment

• sql server probe

Resolution

Edit the custom query by removing the space or as in the example below, add an underscore to the SQL server alias and recreate the checkpoint:

Example: select count(*) as 'current_count' from CA_UIM.dbo.SSRV2AuditTrail