Threshold values unclear in SQL MP for OMI

[Raarth]

Hello,

We are configuring the SQL MP to monitor the SQL databases. Based on the examples for "LogShippingBackupJobs" to monitor the backup jobs status in SQL the threshold values are mentioned as 0.5, 2.5, 4.5 in decimal values.

We are unclear why the threshold values are in decimals? either it uses formula to calculate the value on what basis? or is there any rule for this decimal calculation?

Similar threshold values in decimal given for other monitors as well like "MSSQLServer_3028 - Database Suspect/MSSQLServer_3095 - blocking situations"

Example:

Collection interval: HIGH
Policy: MSSQLServer_3291
Aspect: Microsoft SQL Server Logshipping
CIT: SQL Server
Alarming / Logging: Alarming
Message Category: MSSQLServer_Admin
Severity / Threshold: WARNING / 2.5, MAJOR / 1.5, CRITICAL / 0.5
Message Text: Rule1: Backup job is not enabled in the primary instance. Primary ID = <OPTION(primary_id)>, Primary DB name = <OPTION(primary_db)>, Enabled= <OPTION(enabled) > [Policy: <NAME>]

Regards,

Raarth

[Edward_C_OMi1 · Accepted solution]

Hello  Raarth

This is the way how it was set up by the developers  the same happen to any value.

For example:

Any "0.5" value means that the threshold is set at "0."Because OM alarms occur on <= or >=, the threshold is set to 0.5.

[Raarth]

Hello Edward,

Thanks for writing, the doubt is on what basis these values are calculated in decimals from the SQL Point?

Whether these threshold values are resulted out from the SQL queries/functions or these values are obtained by our agents?

I would like to know before i configure the thresholds as 0.5 > or < on what basis?

Thanks,

Raarth