SpecsModelExploreRequirements
SpecsModelExploreRequirements
Trace Pipeline
Overview
Guide
Twin streams
Links and Communications
IDproduct.platform.observability.trace_pipeline
DescriptionTempo + OTel collectors.
Keytrace_pipeline
Typecomponent
Statusactive
TeamPlatform Engineering
Owner
platform@iotgateway.example
TechnologiesGrafana Tempo, OpenTelemetry Collector, ClickHouse
Tags
Table of contents
Guide
Trace Pipeline
Flow
Correlation
From a metric
Across services
Links and Communications
Requirements

Attributes

retention7d
sampling_ratio0.1

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.

Flow

Correlation

From a log

A log line in the Log Pipeline carries a trace_id; clicking it opens the full trace.

From a metric

A latency spike on a dashboard links to exemplar traces captured at that moment.

Across services

Span context is propagated on every internal call so the trace spans the entire request path.

Traces are retained 7d — long enough to debug a recent incident while keeping the ClickHouse index small and fast.

Links and Communications

1 outgoing link

Outgoing Links(1)

Target objectLabelLink typeRelationRaw idRequiredDescription
Log Pipeline

example-iot.product.platform.observability.log_pipeline

component
correlates with—linksproduct.platform.observability.log_pipeline——

Requirements