- Go to the Add Alarm page
- At the top, choose the type of sensor you want to create an alarm for.
- Choose an element for that particular sensor. Each sensor exposes different elements.
- When you choose an element and a sensor type, the table of deployed sensors (below) is updated with recent values for each location where a sensor has been deployed. 8 hours worth of aggregate history (min, max, avg) is displayed.
- Using the values from the table below, choose a good comparison threshold value for your alarm. Typically, +/- 10% of the maximum value is a good place to start if the monitored service has been operating well and depending on the sensitivity of the alarm that is desired.
- Update the recipients for the alarm. Different Alarm Recipient Groups can be configured.
- Check each of the sensors you would like to apply the alarm to in the table below.
- Click 'Create Alarm' to finish adding the alarm. Or click 'Update Alarm' if you are editing an alarm.
Threshold values will likely be different for each of the different sites (locations) where you have deployed sensors. Best practices is choose an element and look in the table below to see what the Minimum, Maximum and Average values are for each element. When you choose an element the table is updated below for each site. Choosing a value that is slightly (10% or similar) greater then the maximum is recommended if the service you are monitoring is operating correctly.
Most sensors have two (2) operational elements that can be monitored:
This is for tracking sensor errors throughout the system and sensor.
If the sensor stops running or the sensor is unable to communicate with CloudReady servers, this alarm will fire and notify the recipients.
Email Subject Template
The subject of alert emails can be formatted by including options from the following list surrounded by '$':
For example, an email subject might be configured like this: 'A $sensor_type$ sensor alarm has fired after $consecutive_periods$ periods.'
Links in the Email Subject Template
We recently enhanced the alarm email subjects to include support for links. You can now substitute links to either the sensor or the alarm in the email subject:
For example, an email subject might be configured like this: 'A $sensor_type$ has fired: $alarm_link$'