Alerting

Uptrace monitors your metrics and logs continuously and sends a notification the moment a threshold is crossed or an error pattern appears. Monitors are defined in YAML — version-controlled alongside your infrastructure config.

Monitors

The Alerting → Monitors screen lists all configured monitors with their current status. Each row shows the monitor name, type (metric or error), and whether it is currently firing, recovered, or inactive.

Clicking a monitor opens its detail view: the evaluation history, current alert state, and a chart of the monitored value over time. From here you can edit the monitor definition, mute it for a set duration, or close open alerts manually.

Monitor types

Metric monitors evaluate a UQL expression over a rolling time window and fire when the result exceeds a configured threshold. Use them for infrastructure health (CPU, disk, memory, network), HTTP error rates, and span latency percentiles — or any custom metric your services emit.

Error monitors watch log records matching a set of conditions — severity level, message content, or exception type — and fire the first time a new matching pattern appears. Uptrace automatically creates a default error monitor for ERROR and FATAL severity logs.

Notification channels

Alerts are delivered through configurable notification channels: email, Slack, Mattermost, Telegram, Microsoft Teams, PagerDuty, Opsgenie, AlertManager, and custom webhooks.

Each channel supports condition expressions to filter which alerts it receives — a critical Slack channel can ignore low-severity monitors while a catch-all inbox gets everything.

Next steps

• Metric monitors — threshold alerts on infrastructure and tracing metrics
• Error monitors — alerts on log patterns and exceptions
• Notifications — channels, routing conditions, and delivery frequency