Service and location
An incident remains assigned to its monitor and affected checking location.
For DevOps teams
An alert should point to the next useful step.
Uptimo connects confirmed outages with host metrics, two-level rules, delivery history, and public communication.
Uptimo joins these signals as a hosted service. During an incident, a team does not need a wall of charts; it needs the affected service, location, severity, and internal state of the host.
Alert noise is an operational risk of its own
A single threshold forces a choice between too early and too late. One failed check can be a network wobble.
Uptimo confirms outages over several failures. Server rules have warning and critical states, minimum duration, a recovery window, and optional reminders.
What on-call sees first
Severity without guessing
Warning and critical are distinct states. A rule can escalate without notifying every movement in between.
Affected instance
Filesystems, GPUs, sensors, and containers keep alert state individually.
Delivery evidence
Email, SMS, webhook, Slack, Teams, and Telegram have a delivery log.
From signal to quiet recovery
The rules do not cover every possible automation. They keep the alert path from signal to recovery understandable.
Measure a signal
A check or host metric crosses a defined threshold.
Confirm the state
Failure count or minimum duration prevents one spike from immediately creating an incident.
Deliver it correctly
The organisation chooses channels, while each server can inherit, customise, or disable its rules.
Wait for recovery
A recovery window prevents a value near the boundary from flapping between alert and resolved.
Clearly bounded
Important limits
No automatic root-cause claim
Uptimo places signals together but does not claim to know the cause of every correlation automatically.
No process arguments
The agent does not collect complete command lines. Diagnostic depth deliberately stops before potential secrets.
Status updates remain human
Your team publishes the customer-facing explanation, and every update remains visible in the timeline.
FAQ
DevOps-team questions
Can a rule distinguish warning and critical?
Yes. Rules can use both levels with separate thresholds. Minimum duration, a recovery window, and optional reminders complete the state.
Does a full filesystem alert only at server level?
No. Filesystems keep state individually. An absolute minimum free-space value can be used alongside percentage thresholds.
Which channels does Uptimo support?
Email, SMS, webhook, Slack, Teams, and Telegram. Delivery attempts are logged.
Can one server override organisation rules?
Yes. A server can inherit the defaults, use custom rules, or disable its server alerting.
Inspect the rule set before the next alert.
The feature page shows both alert levels, duration, recovery, and rules per measured object.