Metrics
One metric definition — for readouts, guardrails, and dashboards.
Send counters, gauges, and distributions through the same pipeline your flags already feed. Every metric is scoped by service and environment, discoverable with autocomplete, and usable as an experiment metric or a guardrail without redefining it.
FreeIncluded from the Free tier.
checkout_conversioncounter · prodDefine once. Reuse across the platform.
What you get
Why Foredeck for metrics.
Counters, gauges, distributions
Every metric type you need, including latency distributions with p50/p90/p95/p99 from mergeable sketches.
Scoped by service & env
Reserved service and env dimensions plus arbitrary tags, surfaced uniformly for filtering and discovery.
Discovery & autocomplete
A live catalog of metric names and tag values so the right metric is one keystroke away.
One definition, many uses
The same metric powers an experiment readout, a guardrail, and a chart — no duplicate definitions.
How it works
Three steps, one pipeline.
Send metric events via the SDK or the events API.
Find it in the catalog, scoped by service and env.
Attach it to a flag, a guardrail, or a dashboard.
Better together
Works with the rest of the platform.
Experiments
FreeEvery rollout, automatically measured — experiments included free.
Explore Experiments →Services & SLOs
FreeGolden signals and SLOs per service and endpoint.
Explore Services & SLOs →Warehouse-Native Metrics
TeamCompute on the warehouse you already trust — no shadow copy.
Explore Warehouse-Native Metrics →Product Analytics
FreeThe front-end story: page views, clicks, Web Vitals — joined to variations.
Explore Product Analytics →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