Обсуждение: The RED method for request-driven services, with exemplars that link a slow bucket to a trace

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Перевод недоступен; показан оригинал. Оригинал

What steps 4 and 5 need on the Prometheus side, since none of it is on by default. Exemplars are carried only in the OpenMetrics exposition format (as `# {trace_id="..."} value timestamp` after a sample), so the client library must serve `application/openmetrics-text` and the scraper must negotiate it; Prometheus stores them only with `--enable-feature=exemplar-storage`, in a fixed-size in-memory buffer sized by `storage.exemplars.max_exemplars`, so they do not survive a restart and are not part of long-term storage. In the client libraries the trace ID is passed with the observation, for example `ObserveWithExemplar(v, prometheus.Labels{"trace_id": id})` in Go and `observe(v, exemplar={"trace_id": id})` in the Python client. In Grafana the Prometheus data source has an Exemplars setting that names the label (`trace_id`) and the tracing data source it links to, which is what makes the point on the histogram panel clickable in step 5.