| ID | product.platform.observability.trace_pipeline |
|---|---|
| Description | Tempo + OTel collectors. |
| Key | trace_pipeline |
| Type | component |
| Team | Platform Engineering |
| Owner | platform@iotgateway.example |
| Status | active |
| Technologies | Grafana Tempo, OpenTelemetry Collector, ClickHouse |
| Attributes | retention: 7d, sampling_ratio: 0.1 |
| Tags |
Table of contents
Guide
Trace Pipeline
The Trace Pipeline stitches together the spans a single request leaves behind as it crosses services, so you can see where latency or errors come from rather than guessing from per-service metrics.
Sampled, not exhaustive
Storing every span would be enormous and mostly redundant. A head-based sampling ratio of 0.1 keeps a representative slice; errors are tail-sampled so failing requests are always retained.