PH_Rule_DB_7
Enabled
Detects that database server disk I/O latency has reached a critical level (greater than 50 msec) based on 2 successive readings in a 10 minute interval
8
Performance
Storage I/O
No Technique Specified
Application
Windows Performance Monitoring via OMI or Agent, Linux Performance Monitoring via SNMP or Agent, Vcenter Performance Monitoring via VM_SDK
Correlation
Identify the root cause of the performance issue and allocate more resources if needed.
If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.
600 seconds
If the following defined pattern/s occur within a 600 second time window.
ServDiskLatencyCrit
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_DISK_IO_UTIL" AND hostIpAddr IN (Group@PH_SYS_DEVICE_Server) AND diskName NOT IN ("/boot") AND hostIpAddr IN (Group@PH_SYS_APP_DATABASE_SERVER)
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
hostIpAddr,hostName,diskName
This is most typically a numerical constraint that defines when the rule should trigger an incident
(AVG(devDiskRdLatency) >= 50 OR AVG(devDiskWrLatency) >= 50) AND COUNT(*) >= 2
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 = ServDiskLatencyCrit.hostIpAddr,
hostName = ServDiskLatencyCrit.hostName,
diskName = ServDiskLatencyCrit.diskName,
devDiskRdLatency = ServDiskLatencyCrit.AVG(devDiskRdLatency),
devDiskWrLatency = ServDiskLatencyCrit.AVG(devDiskWrLatency)