Alert Template Reference
When an Alert is triggered, Germain looks for a template with a name that matches the SLA that triggers the alert. If such a template is found it is used, otherwise a template with a name that matches the alert-type is used. The generic template for each alert-type must exist.
Currently the only alert type is SLA.
Germain Workspace > Left Menu > System> Alert Templates
The template processing is implemented using the Freemarker template engine. Any construct that is allowed by Freemarker will be supported by Germain. The Freemarker documentation is available at http://freemarker.org/docs/
The context data consists of the following root data objects.
- customerName (String)
- environmentName (String)
- alertType (String)
- alertGroup (String)
- context (Object)
- firstOccurred (Date)
- occurrences (Integer)
The details of each of these data objects are given in the following paragraphs.
The context is different from all of the other context data objects in that its structure and contents depend on the alertType. Each alertType can have its own context data types, but for a given alertType the context data will always have the same structure. In the following paragraphs we will define the contents of the context data object for each of the current alertTypes.
- alertType: SLA
For SLA alerts, the context objects have the following structure:
- fact (Object)
Can be one of the following types (See the Fact Type Definitions)
Note: For statistical SLA alerts the fact object is not available.
- AVAILABILITY (Object)
- EVENT (Object)
- METRIC (Object)
- NETWORK_LATENCY (Object)
- TRANSACTION (Object)
- UX_EVENT (Object)
- UX_METRIC (Object)
- UX_TRANSACTION (Object)