Alerting & monitoring

Know before your users do

When something breaks, you should hear about it before your users do — not from a support ticket. Uptrace monitors metrics, spans, and logs in one platform and routes alerts to the right channel with conditions you control.

Set up your first alert Schedule a demo

14-day free trial · No credit card required

Monitors for every signal

Choose a fixed threshold, detect unusual metric behavior, watch for error patterns, or track an SLO error budget.

Threshold, anomaly, outlier, and forecast monitors for metrics
Error monitors: trigger on exceptions, log severity, or message patterns
SLO monitors: alert when error budget burn-rate rules fire
ERROR and FATAL monitors created automatically — no setup needed
Filter by any attribute: service, environment, host, operation
Group by service, region, or custom dimension to split notifications

Cover every layer of your stack

From CPU and disk to PostgreSQL query latency and HTTP error rates — infrastructure and application in one monitor, no extra tools

Host metrics: CPU load, memory, filesystem usage, disk I/O, network errors
Application spans: p50/p99 latency, throughput, and error rate per operation
Database queries: alert on slow SELECT queries exceeding a latency threshold
Log events: alert when error count exceeds a threshold per service or region
Any Prometheus or OpenTelemetry metric supported out of the box

Live monitors active

Infrastructure

58%OK

Application

0.2%OK

Database

76 msOK

Logs

8/minOK

Metrics

2.0k/sOK

Alert: DB query time exceeded 100 ms

Route to the right channel

Route production alerts to PagerDuty and staging alerts to Slack from one monitor.

Email, Slack, Teams, PagerDuty, ServiceNow, Alertmanager, webhooks, and more
Filter channels by environment, hostname, service, or monitor name
Prod to PagerDuty, staging to Slack — from a single monitor definition
Alert body includes metric values, error samples, and affected attributes
Recovery notifications when metric or SLO conditions resolve

Silence the noise, not the signal

Adaptive intervals grow over time — a lingering alert reminds you daily, not every 15 minutes

Metric and SLO interval: starts at 15 min, doubles every 3 alerts, caps at 24 h
Error interval: starts at 1 h, doubles every 2 alerts, caps at 1 week
Recovery notification when a metric or SLO alert resolves
Channel conditions filter low-priority alerts away from on-call noise

Alerts as code

Write monitors in YAML, commit to git, apply with Terraform — alerting config becomes reproducible and version-controlled

YAML definitions for threshold, anomaly, outlier, forecast, error, and SLO monitors
Terraform provider manages monitors, channels, and routing
Import monitor YAML through the Uptrace UI
Copy alerting config from staging to production in one step
Alert names support Go templates referencing any span attribute

Better together

Each signal is more powerful when correlated with the others. Uptrace stores traces, logs, and metrics in one place, no tool-switching, no data gaps.

Distributed tracing

Find the exact span that broke your request, across every service and database call.

Log management

Search structured logs at any scale and jump from any span to its logs in one click.

Metrics

PromQL-compatible metrics with no cardinality limits and automatic dashboards.

Common questions, clear answers

What is the difference between a threshold monitor and an error monitor?

A threshold monitor evaluates a numeric query against a fixed limit, such as CPU usage above 80%. An error monitor watches for matching log or exception patterns. Other metric monitors can detect anomalies, outliers, or forecast crossings.

Can I alert on span and trace data, not just infrastructure metrics?

Yes. Uptrace exposes span data as built-in system metrics — uptrace_tracing_spans, uptrace_tracing_logs, and uptrace_tracing_events — which you can use in metric monitors. This lets you alert on p99 latency for a specific operation, the error rate on an HTTP endpoint, or the number of failed database queries per minute.

How does Uptrace avoid alert fatigue?

The default notification interval grows over time. Metric and SLO alerts start at 15-minute reminders and double every three notifications up to a 24-hour maximum. Error alerts start at 1 hour and cap at 1 week. Metric and SLO alerts send recovery notifications when their conditions clear.

Can I define monitors as code instead of through the UI?

Yes. Write monitor definitions in YAML and import them through the UI. The Uptrace Terraform provider also manages monitors, notification channels, projects, and team access.

Which notification channels does Uptrace support?

Uptrace supports email, Slack, Google Chat, Mattermost, Microsoft Teams, PagerDuty, ServiceNow, Opsgenie, Telegram, Pushover, Alertmanager, incident.io, and webhooks. Each channel supports conditional routing, so one monitor can send production alerts to PagerDuty and staging alerts to Slack.

Ready to alert before users notice?

Deploy in minutes with Docker. Open source. Fixed pricing. Your data stays on your infrastructure.

Set up your first alert

14-day free trial · No credit card required

Learn more

Documentation Pricing Schedule a demo