Understanding the "SQL PI Experiencing Errors" Rules (4232581)

This article explains how the "SQL PI Experiencing Errors" rules function to determine when the alarm is raised.

The "SQL PI Experiencing Errors" rules are triggered when SQL PI data collection is unavailable due to errors related to OLAP availability.

Data Gap Detection

Each monitored agent type (SQL Server, Oracle, SSAS) uses a hidden Agent Status Property (ASP) to determine how long a delay in SQL PI data collection is tolerated before triggering the rule.

• SQL Server: paecOlapAvailabilityDataGapMinutes

• Oracle: spiecOlapAvailabilityDataGapMinutes

• SSAS: ssasOlapAvailabilityDataGapMinutes

If SQL PI data has not been written to the performance repository within the configured threshold (default: 30 minutes) the alarm fires. 

These properties often appear as -2147483648 in the Agent Status Properties UI, which represents an unset (null) value using Java’s minimum 4-byte integer.

Related Rules

Depending on the monitored technology, the following rules may trigger using the same logic:

• DBSS - SQL PI: SQL PI Experiencing Errors (SQL Server)

• DBO - SQL PI: SQL PI Experiencing Errors (Oracle)

• SSAS - PI Experiencing Errors (SSAS) {This depends on the SQL Server agent also functioning with PI}

Additional Information:

Note: A value of -2147483648 indicates the property is not explicitly set and defaults to the internal value (usually 30 minutes for data gap threshold).