PH_Rule_Environ_1
Enabled
Detects that key UPS operational metrics are outside of normal operational range
9
Availability
UPS
No Technique Specified
Environmental
Any UPS Device via SNMP
Correlation
Identify the root cause and solve the issue
If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.
300 seconds
If the following defined pattern/s occur within a 300 second time window.
LowBattery1
This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.
This is the query logic that matches incoming events
eventType = "PH_DEV_MON_UPS_METRIC" AND upsAdvOutputFreq IS NOT NULL AND upsAdvOutputVoltage IS NOT NULL
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
hostIpAddr, hostName
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT (*) >= 2 AND ( AVG(upsAdvOutputFreq) <= 55 OR AVG(upsAdvOutputFreq) >= 65 OR AVG(upsAdvOutputVoltage) < 110 OR AVG(upsAdvOutputVoltage) > 125 OR AVG(upsAdvOutputLoad) >= 50)
This section defines which fields in matching raw events should be mapped to the incident attributes in the resulting incident.
The available raw event attributes to map are limited to the group by attributes and the aggregate event constraint fields for each subpattern
hostIpAddr = LowBattery1.hostIpAddr,
hostName = LowBattery1.hostName,
upsAdvOutputFreq = LowBattery1.AVG(upsAdvOutputFreq),
upsAdvOutputVoltage = LowBattery1.AVG(upsAdvOutputVoltage),
upsAdvOutputLoad = LowBattery1.AVG(upsAdvOutputLoad)