The gateway allows rule functions and actions to escalate and repeat. However, it may make sense to be able to repeat and/or escalate without having to define this in the action itself. This article talks about an alternative method using Alerting and Effects in the Gateway Setup Editor. |
The full technical details on the configuration can be found in the Gateway documentation's Alerting section however the following is a real world example as to how an alerting hierarchy would be configured. In this example I am alerting to both application and infrastructure teams without modifying rules. Screenshot of Alerting Section as it appears in the GSE.In the aforementioned configuration it is assumed that there are Managed Entities that are Infrastructure based, and others that are application based, but this is not a requirement for configuration. Each hierarchy allows for the specification of one or more levels, which is where notification and repetition is configured. In the following screenshot I have configured the CPU alerting level to escalate Critical alerts, as well as repeating this in an Escalation.
Alerting XML Example
< alerting > < hierarchy name = "Application Hierarchy" > < priority >1</ priority > < levels > < level > < match > < managedEntityAttribute >Environment</ managedEntityAttribute > </ match > </ level > < level > < match > < managedEntityAttribute >Component</ managedEntityAttribute > </ match > </ level > < level > < match > < samplerName ></ samplerName > </ match > </ level > </ levels > < alert name = "Trading" > < critical > < level > < notification > < effect ref = "alertEngine" ></ effect > < role > < role ref = "TradingManager" ></ role > </ role > < clear >true</ clear > </ notification > </ level > < alwaysNotify >true</ alwaysNotify > </ critical > < alert name = "FIX" > < warning > < level > < notification > < effect ref = "alertEngine" ></ effect > < role > < role ref = "FIXSupport" ></ role > </ role > </ notification > </ level > </ warning > < critical > < level > < notification > < effect ref = "alertEngine" ></ effect > < role > < role ref = "FIXSupport" ></ role > </ role > </ notification > < escalationInterval >300</ escalationInterval > </ level > < level > < notification > < effect ref = "alertEngine" ></ effect > < role > < role ref = "FIXSupport" ></ role > </ role > </ notification > </ level > </ critical > < alert name = "FKM" > < warning > < level > < notification > < effect ref = "alertEngine" ></ effect > < role > < role ref = "FIXSupport" ></ role > < infoType >Email</ infoType > </ role > </ notification > </ level > </ warning > < critical > < level > < notification > < effect ref = "alertEngine" ></ effect > < role > < role ref = "FIXSupport" ></ role > < infoType >Email</ infoType > </ role > </ notification > </ level > </ critical > </ alert > </ alert > </ alert > < alert name = "Database" > < alert name = "Oracle" > < alert name = "OracleDB" ></ alert > </ alert > < alert name = "Sybase" > < alert name = "SybaseDB" ></ alert > < alert name = "SybaseSvr" ></ alert > </ alert > </ alert > </ hierarchy > < hierarchy name = "Infrastructure Hierarchy" > < priority >2</ priority > < levels > < level > < match > < managedEntityAttribute >Environment</ managedEntityAttribute > </ match > </ level > < level > < match > < samplerName ></ samplerName > </ match > </ level > </ levels > < alert name = "Infrastructure" > < critical > < level > < notification > < effect ref = "alertEngine" ></ effect > < role > < role ref = "InfraTeam" ></ role > < infoType >Email</ infoType > </ role > </ notification > </ level > < alwaysNotify >true</ alwaysNotify > </ critical > < alert name = "CPU" > < warning > < level > < notification > < effect ref = "alertEngine" ></ effect > < role > < role ref = "InfraTeam" ></ role > < infoType >Email</ infoType > </ role > </ notification > </ level > </ warning > < critical > < level > < notification > < effect ref = "alertEngine" ></ effect > < role > < role ref = "InfraTeam" ></ role > < infoType >Email</ infoType > </ role > </ notification > < escalationInterval >300</ escalationInterval > </ level > < level > < notification > < effect ref = "alertEngine" ></ effect > < role > < role ref = "InfraTeam" ></ role > < infoType >Email</ infoType > </ role > </ notification > </ level > </ critical > </ alert > < alert name = "Disk" > < warning > < level > < notification > < effect ref = "alertEngine" ></ effect > < role > < role ref = "InfraTeam" ></ role > < infoType >Email</ infoType > </ role > </ notification > </ level > </ warning > < critical > < level > < notification > < effect ref = "alertEngine" ></ effect > < role > < role ref = "InfraTeam" ></ role > < infoType >Email</ infoType > </ role > </ notification > </ level > </ critical > </ alert > < alert name = "Network" > < warning > < level > < notification > < effect ref = "alertEngine" ></ effect > < role > < role ref = "InfraTeam" ></ role > < infoType >Email</ infoType > </ role > </ notification > </ level > </ warning > < critical > < level > < notification > < effect ref = "alertEngine" ></ effect > < role > < role ref = "InfraTeam" ></ role > < infoType >Email</ infoType > </ role > </ notification > </ level > </ critical > </ alert > </ alert > </ hierarchy > </ alerting > |
|
Further Reading
|
Comments
0 comments
Please sign in to leave a comment.