Alerts and notifications

Route the signal without losing the incident

E4S can use email, Telegram, push, and sound channels where configured. User preferences determine delivery choices; deduplication reduces repeated notifications for the same condition. The original check and event history remain available for review.

Illustrative response workflow; no customer incident is depicted.

When an alert arrives

1. Verify the asset and active workspace.
2. Read the timestamp and latest completed check.
3. Compare previous observations and related service state.
4. Coordinate the next action with the responsible operator.

Missing delivery is a separate issue from asset health. Use the alert investigation guide to follow the decision trail.