Alerting & Incident Management

See the Problem Before Your Users Do

Rule-based alerts watch metric thresholds and health events; when one fires it reaches you by email, webhook and in-panel notification — with silences and maintenance windows to match.

One flow from rule to notification

Threshold → firing → notification → acknowledgement; the whole chain is followed on one screen.

Noise control

A time-boxed silence suppresses only the notification; the alert keeps evaluating normally in the background.

What's Inside

The Full Alerting Loop

From defining a rule to reviewing incident history, every step happens in the panel.

Rule-Based Alerts

Define rules on metric thresholds, health checks or event types; a useful default rule set ships with the panel.

Multi-Channel Notification

Email (SMTP), webhook and in-panel notification; channel settings are managed in the panel and secrets come back masked.

Silences & Maintenance

Define a time-boxed silence for planned maintenance; when the window ends the silence lifts itself.

Acknowledgement

Take ownership of a firing alert; who acknowledged it and when is recorded.

Channel Testing

Send a test notification before a channel goes live — no surprise webhook failures at the critical moment.

Event Timeline

Alerts, health events and system events converge into one stream, making retrospectives straightforward.

From Alert to Action

The alerting engine doesn't just inform you — it is the signal source for the automation engine.

Firing alerts land in an event pool; automation rules read that pool to trigger drain, reboot and power actions.

Restore a modified default rule to its factory value in one click, and bring back one you hid.

SMTP passwords and webhook tokens are masked in API responses; the panel never returns a secret in clear text.

The nightly drift, surface and backup-freshness checks write their findings into the panel's own event stream — no separate monitoring system to stand up.

Want to see it live on your cluster? Get in touch!
%