PH_Rule_Trap_2
Enabled
Detects a medium severity trap from NetApp Filers. This trap can be cleared by a corresponding event.
7
Availability
Storage
No Technique Specified
Storage
NetApp via SNMP Trap
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.
600 seconds
If the following defined pattern/s occur within a 600 second time window.
MedSevTrap
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 CONTAIN "NetApp-" AND eventSeverityCat = "Medium" AND errorNo 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
reptDevIpAddr, hostName, eventType,errorNo
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT (*) >= 1
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 = MedSevTrap.reptDevIpAddr,
hostName = MedSevTrap.hostName,
compEventType = MedSevTrap.eventType,
errorNo=MedSevTrap.errorNo