Service monitoring
Requests, errors, and latency — per service, per endpoint.
Services auto-register from your telemetry. Get the golden signals per endpoint aggregated to the service, set latency and availability SLOs, and see p90/p95/p99 overlays on the charts at the top of every service page.
FreeIncluded from the Free tier.
checkout-apiprod · SLO 99.9%The RED signals — and the SLO to hold them to.
What you get
Why Foredeck for services & slos.
Auto-registered services
A service/env registers itself on first sight from any telemetry — no manual setup.
Per-endpoint golden signals
Requests, errors, and latency at the resource (endpoint) level, aggregated to the service from mergeable rollups.
SLOs
Set latency and availability objectives over rolling windows and track burn against them.
Percentile overlays
p90 and p99 tracked on top of p95, graphed together and individually togglable.
How it works
Three steps, one pipeline.
Emit service metrics, logs, or spans — the service registers itself.
Define the latency/availability objective you want to hold.
Go service → endpoint → the traces behind a regression.
Better together
Works with the rest of the platform.
Tracing
FreeFollow one call across every service — spans stamped with the variation.
Explore Tracing →Logs
FreeSearch logs in release context — OTLP-native, correlated to flags.
Explore Logs →Metrics
FreeDefine a metric once, use it everywhere.
Explore Metrics →One object, one pipeline. The same rollout you ship is automatically measured, guarded, and — when it breaks — traceable, because every signal is joined to the flag and variation the unit was in.
Get in