Skip to content

Warning and critical kept apart — per object, not per server.

Two-level alerting

A single threshold forces a choice between too early and too late. Uptimo separates warning and critical per rule, with minimum duration, recovery time and repeat interval — a value oscillating around the threshold does not produce an alert storm.

Levels
warning and critical
Rules
per filesystem, GPU, container
Channels
6
The rule set as it looks in the product: two levels per metric, duration in minutes, all one form.
The rule set as it looks in the product: two levels per metric, duration in minutes, all one form.

What matters here

Per object, not per host

Filesystems, GPUs, sensors and containers alert individually. A full /var never masks a filling /data.

An absolute floor

90 % of 4 TB is not a problem, 90 % of 20 GB is. Next to the percentage there is a minimum amount of free space — plus overrides per mountpoint or device.

Escalation without noise

A firing warning that reaches critical sends an escalation. The way back stays quiet until recovery.

Six channels

Email, SMS, webhook, Slack, Teams and Telegram — every delivery logged.

Global or per server

Organisation-wide defaults, per-server overrides, or alerting switched off for one host.

FAQ

Common questions about Two-level alerting

Why are warning and critical separate?

You can react early to a trend while keeping a second, unambiguous escalation level.

Can rules change per server?

Yes. A server can inherit organisation defaults, use custom rules or disable alerting.

Which channels are available?

Email, SMS, webhook, Slack, Teams and Telegram. Deliveries are logged.

Test it with your own system.

A first monitor shows you the flow without example data.

Start for free