Templates (Alerts or Reports)

Feature

Templates define the appearance and content of Alerts or Reports when automatically created and sent by Germain UX. Template Editor (starting in 2024.1) is now making it very easy for clients to create their own alert or report.

Some of the features making Template Editor easy:

• Template “Preview” with real data

• Autocomplete inside editor to help with context variables/functions

• Context variable table shows a preview of what's available

• Inline error highlighting

Video overview of Germain UX’s Template Editor:

Context Data

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 provided in the following paragraphs. The 'context' differs from all 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 maintain the same structure. In the subsequent 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)

Fact Definitions

More details on Germain UX’s Data Model and Fact.

Notifications

See how to enable Notifications (email, sms, watch) using these templates.

Service: Management

Feature Availability: 2014.1 or later