Skip to content

Service health,
from map to alert.

See which services talk to each other, inspect changes in health and send alerts to the tools your team already uses.

Start with the connection.

The service map shows relationships observed in telemetry from instrumented services. Inspect a service or connection to follow requests, error rate, latency and HTTP responses.

Related error groups help you see repeated failures. Missing data remains visible, so an empty window does not look like a healthy one.

Understand the health model

checkout to payments

requests/min
240
p95 latency
180 ms
errors
1.2%

Error rate above 1%

Sent to Slack

Health and errors

Service dependencies, recent health history, HTTP status codes and groups of repeated errors.

Rules and delivery

Rules for errors, latency, selected metrics, matching logs and stale telemetry. Direct delivery to Slack, Teams, email, PagerDuty and webhooks.

Focused history

Compact health summaries and selected evidence in PostgreSQL, with a default seven-day monitoring window.

Where it fits

A focused starting point for teams choosing service health monitoring and alerting. Keep a separate backend if you need a searchable archive of every raw log and trace.

Connect your services.

Use your existing Collector or the included Kubernetes setup.

Get started