Set up alarms and notifications

Create a rule

1. Open Alarms, add a rule and select its monitor or series.
2. Choose an alarm and recovery condition. A separate recovery threshold and a minimum duration help avoid alerts for brief fluctuations.
3. Select all active destinations or a specific selection, save and check a test message. Under Alarms → Rules, search and filters cover every active rule; use the page controls for more results. Paused rules remain available.

Which rule fits?

Use thresholds for numerical values, missing-data rules for a series, heartbeat rules for device contact, state rules for exact states, text rules for messages and run rules for job outcomes.

• Numeric thresholds and hysteresis

  Use different alarm and recovery thresholds to avoid repeated messages around a limit.

• Alarms for missing data and device heartbeats

  Be notified when readings or device heartbeats stop arriving.

• State alert rules

  Alert on a specific yes/no value or named operating state.

• Text and event rules

  Find relevant words or severity levels in short event messages.

• Job and workflow run alerts

  Get notified about failed, aborted, overlong or missing job and workflow runs.

Connect Telegram

1. Create a Telegram destination under Notifications and open its link to @MetriBeaconBot.
2. Send the supplied /start command in your private chat. The connection activates the destination and sends a confirmation.
3. Send a test and select this destination in your rule.

Email and other channels

Confirm an email destination before using it. Other available channels have their own setup fields under Notifications. Test the destination and check the message yourself. All channels share the delivery allowance and ten test messages per hour.

Planned interruptions

Pause stops rule evaluation; mute keeps evaluation but stops delivery. Rule maintenance pauses new alarm and recovery transitions. Read the maintenance guide before planning an interruption.

If a message is missing

Check the rule’s source, current values and notification targets. A configured active target does not prove successful delivery. Its latest failure or planned retry is visible beside the last successful provider handover. Check the target settings and send a test after correcting them. A provider handover does not confirm inbox receipt. Suppressed deliveries explain pauses, maintenance or reached allowances.

Open a specific incident and choose Logs. Associated sources are searched from 15 minutes before to five minutes after its start. New incidents preserve the original sources and log-rule filters; older incidents identify current associations. Widening to the workspace is explicit. Open the explorer to adjust filters and see overlapping incident markers; links preserve your investigation window. Searched logs are context, not the original triggering evidence.

SMS and calls through MetriBeacon

Create an SMS or phone destination and choose Through MetriBeacon when your account is explicitly approved. Enter your number and verify it with the received code. Verification and tests use the same allowance as alarms. Inspect remaining day/month allowances and delivery results; then explicitly assign the destination to your rules or escalation policy. Country, price, segment and cost limits can block phone delivery while other channels continue. You can continue using your own provider. Public status-page SMS requires your own Twilio account.