Log management
What do the logs say — for this variation?
Point your OTLP collector or the SDK at Foredeck and search logs with a live tail, facets, and full-text — each line stamped with the flag and variation its unit was in. Ingest is decoupled from indexing, so you send everything and index what matters.
FreeIncluded from the Free tier.
checkout-apilive tail · errorEvery log line, in the release context that produced it.
What you get
Why Foredeck for logs.
OTLP-native ingest
One-line exporter change points existing collectors at Foredeck — plus a native intake for the SDK and simple forwarders.
Exposure-stamped
Each log is joined to the flag/variation its unit was in, so “what do the logs say for treatment?” is a filter.
Explorer + live tail
Full-text search, facets, and a WebSocket live tail — with processors, exclusion filters, and log-based metrics.
Tiered retention
3-day search on Free, extended retention and archives on Pro, enforced per account.
How it works
Three steps, one pipeline.
Send logs over OTLP or the native intake.
Filter by service, status, flag, and free text with a live tail.
Jump from a log line to its trace, and back.
Better together
Works with the rest of the platform.
Tracing
FreeFollow one call across every service — spans stamped with the variation.
Explore Tracing →Services & SLOs
FreeGolden signals and SLOs per service and endpoint.
Explore Services & SLOs →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