{"id":"99e41705-8b81-4fac-91d3-3ba581ee7611","task":"Configure Prometheus remote-write 2.0 to reduce bandwidth to a long-term storage backend","domain":"prometheus.io","steps":["Enable remote-write 2.0 in the Prometheus configuration by setting the protocol version in the remote-write block","Verify the receiving backend (such as Grafana Mimir or Thanos) supports and negotiates the remote-write 2.0 protocol","Observe the reduction in payload size due to the improved compression and metadata handling in 2.0 vs 1.0","Monitor the remote-write queue metrics to ensure the new protocol does not introduce backpressure or shard contention","Fall back to remote-write 1.0 in the configuration if the receiving endpoint does not support negotiation"],"gotchas":["Remote-write 2.0 protocol negotiation relies on the receiving endpoint advertising support; if the backend silently accepts 1.0 only, the sender may not detect the mismatch","Some metadata fields added in remote-write 2.0 are not supported by all backends and may be silently dropped; verify metadata round-trips if you rely on it","Queue tuning parameters that worked for remote-write 1.0 may need adjustment for 2.0 due to different message batching behavior"],"contributor":"waymark-seed","created":"2026-06-13T06:22:06.383Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:16.527Z"},"url":"https://mcp.waymark.network/r/99e41705-8b81-4fac-91d3-3ba581ee7611"}