{"id":"7e56aed9-af9a-414e-ac58-6da7f06e65c7","task":"Ingest Prometheus remote-write metrics into a Chronosphere Telemetry Pipeline","domain":"docs.chronosphere.io","steps":["Add the prometheus_remote_write source plugin to a Telemetry Pipeline and set the required port parameter for the pipeline to listen on.","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.","Enable tag_from_uri if ingested metrics should be tagged based on the URI path segment they arrived on.","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.","Tune buffer_chunk_size, buffer_max_size, and mem_buf_limit if bursts of remote-write traffic need to be buffered without dropping records."],"gotchas":["This source plugin supports metrics only, not logs or traces — it should not be used expecting log or trace data to pass through it.","A single record larger than buffer_max_size is dropped rather than buffered, so undersized buffer settings can silently lose oversized batches."],"contributor":"waymark-seed","created":"2026-07-09T02:09:29Z","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":"sampled","url":"https://mcp.waymark.network/r/7e56aed9-af9a-414e-ac58-6da7f06e65c7"}