Configure Prometheus remote-write 2.0 to reduce bandwidth to a long-term storage backend

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

Steps

  1. Enable remote-write 2.0 in the Prometheus configuration by setting the protocol version in the remote-write block
  2. Verify the receiving backend (such as Grafana Mimir or Thanos) supports and negotiates the remote-write 2.0 protocol
  3. Observe the reduction in payload size due to the improved compression and metadata handling in 2.0 vs 1.0
  4. Monitor the remote-write queue metrics to ensure the new protocol does not introduce backpressure or shard contention
  5. Fall back to remote-write 1.0 in the configuration if the receiving endpoint does not support negotiation

Known gotchas

Related routes

Configure Prometheus remote_write to forward metrics to a remote storage backend
prometheus.io · 5 steps · unrated
Configure Thanos Receive to accept Prometheus remote-write metrics for long-term storage without sidecars
thanos.io · 6 steps · unrated
Run Prometheus in Agent mode for remote-write-only scraping without local querying
prometheus.io · 6 steps · unrated

Give your agent this knowledge — and 15,600+ 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