Alert (email and sms)
In Germain, alerting is a core functionality that enables your teams to react to SLA breaches in monitored environments, whether they are Technology SLAs, Business Process SLAs or User Experience SLAs. These alerts can be triggered by basic ingested data, correlated data, query mechanisms ( see Automation - SQL execution ) and HTTP actions ( see Automation - Http(s) execution ).
There are some key concepts in order to fully understand how alerting works, but in a nutshell, once a data point is ingested and an SLA evaluated for that data point, we are able to configure an action to trigger, one of these actions types is an AlertAction which will notify a target group of users - Distribution List - by sending a message defined by a template.
Steps to configure an Alert
In order to configure alerting you'll need to follow these steps:
Define a distribution list
Create the AlertAction
Associate the AlertAction with an SLA
Create or customize a Template
Alert Object Reference
Workspace Field Label
Unique Action Name
Name of the alert distribution group for this alert.
String, matching an existing Distribution List
Execute via Engine
*Calculated Field* if set to true, allows target server be defined
Triggered by SLAs
*Calculated Field* Collection of SLAs this action is configured for
Quiet Time Used
If set, alerts of this type will not fire again during the quiet time period after the initial occurrence.
For More details please see our dedicated documentation page: Quiet Time
Quiet TIme Period
Quiet time period (in seconds) to use for this alert. If set to 0, will use default quiet time period.
Integer ( seconds )
Notify On Success
Notify On Failure
Used in combination with limitInterval to define upper limit on how many times to execute this action.
Used in combination with limitCount to defines interval during which upper limit applies.
String, one of the following values:
Number of Retries
*Advanced Field* Number of retries which needs to be performed of incase of a delivery failure.
Germain Workspace > Left Menu > System>Alert Templates
More details: Alert Template Reference
As an example, here what i did to setup an Email Alert that needs to be sent whenever CPU Usage SLA is violated/exceeded.
I'll start by confirming that I have a CPU Usage KPI by navigating to Analytics > KPIs
Here I have confirmed I have the KPI configured and that there is also an SLA defined.
Open the Wizard: Germain Workspace >left menu>Automation>Alert page> click + icon
Setup the Alert
Distribution: Either select an existing distribution or create a new one by clicking the + sign and following the distribution creation wizard.
Setup the SLA
SLA: Select the CPU Usage SLA that was previously configured or create a new SLA
Configure your Alert Template (left menu>System) and select CPU Usage
We now have a fully configured alert that will be sent out once a CPU Usage SLA breach is identified
Note that this AlertAction is not restricted only to CPU Usage SLA and can be reused across other SLAs, if we would like to also notify the same distribution of Memory Usage SLA breaches we could click on the + sign next to Triggered by SLAs and link it to any other existing SLA by selecting as many SLAs you would like to link with this Action in the displayed Wizard: