Ingest Prometheus remote-write metrics into a Chronosphere Telemetry Pipeline

domain: docs.chronosphere.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Add the prometheus_remote_write source plugin to a Telemetry Pipeline and set the required port parameter for the pipeline to listen on.
  2. Point Prometheus's (or another remote-write client's) remote_write configuration at that pipeline endpoint, adjusting the uri parameter if it was customized away from the default /api/prom/push.
  3. Enable tag_from_uri if ingested metrics should be tagged based on the URI path segment they arrived on.
  4. Configure TLS options (tls, tls.verify, tls.ca_file, tls.crt_file, tls.key_file) if the pipeline needs to terminate TLS for incoming remote-write traffic.
  5. Tune buffer_chunk_size, buffer_max_size, and mem_buf_limit if bursts of remote-write traffic need to be buffered without dropping records.

Known gotchas

Related routes

Ingest OpenTelemetry exemplars from a Prometheus-instrumented application and query them in Grafana to jump from metric spikes to traces
grafana.com/docs/grafana · 6 steps · unrated
Configure Prometheus remote_write to forward metrics to a remote storage backend
prometheus.io · 5 steps · unrated
Configure Prometheus recording rules to pre-aggregate SLO burn rate windows for efficient querying
opentelemetry.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