{"id":"d660067e-1a4d-456f-bfe2-81f04a93c07b","task":"Configure Thanos Receive to accept Prometheus remote-write metrics for long-term storage without sidecars","domain":"thanos.io","steps":["Run `thanos receive` with `--tsdb.path`, `--grpc-address`, `--http-address`, and `--remote-write.address` to start a receiver that exposes a Prometheus-compatible remote-write endpoint at `/api/v1/receive`.","Point each Prometheus instance's `remote_write.url` configuration at the Receive endpoint so samples are pushed directly, eliminating the need for a Thanos Sidecar.","Create a hashring configuration file (JSON, listing receive endpoints) and pass it via `--receive.hashrings-file` so incoming write requests are routed/distributed to the correct ingesting node(s).","Set `--receive.local-endpoint` on each node to identify itself within the hashring; a node with hashring config and a local endpoint runs in RouterIngestor mode (routes and ingests), a node with hashring config but no local endpoint runs RouterOnly, and a node with no hashring config runs IngestorOnly.","Set `--receive.replication-factor` (typically an odd number such as 3) to control how many nodes each incoming write is replicated to for durability.","Configure `--objstore.config-file` so the receiver periodically uploads its local TSDB blocks to object storage, and point Thanos Query and Store Gateway at that same bucket for long-term queries."],"gotchas":["The number of endpoints in the hashring must exceed the configured `--receive.replication-factor`, otherwise writes fail with an \"amount of endpoints needs to be larger than replication factor\" error.","Because a node's behavior depends on whether hashring config and `--receive.local-endpoint` are both present, misconfiguring one of them silently changes the node's role (RouterOnly vs IngestorOnly vs RouterIngestor) rather than producing an obvious error.","Receive's replication writes identical samples (same timestamps and values) to replicas, so use the default `one-to-one` vertical-compaction dedup for overlap — the `penalty` dedup algorithm is intended for independently-scraped Prometheus HA pairs, not Receive replication."],"contributor":"waymark-seed","created":"2026-07-08T17:34:57.823Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/d660067e-1a4d-456f-bfe2-81f04a93c07b"}