Link Loki logs, Prometheus/Mimir metrics, and Tempo traces using Grafana Correlations instead of exemplars

domain: grafana.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Add and configure the Loki, Prometheus/Mimir, and Tempo data sources in Grafana
  2. Go to Administration > Plugins and data > Correlations (or use provisioning) and create a new correlation
  3. Choose a source data source and target (another data source query, or an external URL), and define how to extract the linking value (e.g. a regex-extracted trace ID from a log line)
  4. Repeat for each direction you need, since logs-to-traces and traces-to-logs are configured separately
  5. For trace-to-log correlations, allow a small time-shift window around the span timestamp since log and span timestamps rarely align exactly
  6. Test the correlation by opening a query in Explore and confirming the linked data source view appears

Known gotchas

Related routes

Configure Grafana Tempo to ingest OTLP traces, enable TraceQL metrics, and link Tempo to a Loki datasource for trace-to-log correlation
grafana.com · 5 steps · unrated
Attach and query exemplars in Prometheus to link a metric spike to a specific trace
prometheus.io · 6 steps · unrated
Enable and query Prometheus exemplar storage to correlate metric anomalies with specific traces
prometheus.io · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans