Schedule alarm evaluation, select supervised entities, and notify the right recipients.
A watchdog or alarm instance turns alarm logic into an operational workflow. The current editor manages scheduling, scope, actions, and access separately so one alarm template can support several teams or site groups.
Each watchdog instance connects a named operational purpose to an alarm template.
Select the alarm template that represents the condition. The template defines the compatible alarm route and supported evaluation periods.
Review:
Use the site's operational timezone unless the organisation has a documented central convention.
Each action contains:
Create both an activation and a clear notification when recipients need to know that service has recovered.
Add the devices or roles that the watchdog should evaluate. Saving the general settings without contained entities does not create a useful operational scope.
Assign roles that may view the instance, edit it, or manage its viewers. These rights are separate from notification recipients.
The current message editor can use:
Test activation and recovery
A complete test proves the rule activates, the intended recipients receive the message, the condition clears, and the recovery action is delivered. Testing only the save button is insufficient.
| Symptom | Check |
|---|---|
| No evaluations | Active dates, period, timezone, and template. |
| Evaluations but no affected sites | Contained devices or roles and alarm selection. |
| Alarm active but no message | Trigger state, action delay, channel, and recipient resolution. |
| Wrong language | Action language and contact-derived recipient strategy. |
| User cannot edit | Viewer entry and editing right for that role. |