Bartlomiej Plotka

We discussed this [in the DevSummit](https://docs.google.com/document/d/11LC3wJcVk00l8w5P3oLQ-m3Y37iom6INAMEu2ZAGIIE/edit#heading=h.4hhksqycl1d8) and there was not strong opinion either way, including to reject this. I personally would lean on helping Cortex and AWS teams to use...

Is it perhaps related to https://github.com/prometheus/prometheus/issues/13939, so if the Prometheus OOMs you have to delete the WAL (and reduce your scrape load) OR change memory limits if you want to...

Thanks for reporting. This error is visible where? In Prometheus logs? Is it related to scraping? Remote Write? Remote Read? Do you see any other problems other than a error...

Nice, thanks! But I wonder if we can revisit the semantics of format and this flag to give easy, safe and explicit configuration. E.g. in this PR user might now...

Then "migration" does not need any specific header values - user does not need to know it. User would just set 1.0:snappy preference (only one thing) to clients to limit...

Well the supported protocol "preference" for server side is generally solving all the use cases and it's not too difficult to grasp, so single flag `--web.remote-write-receive.protocols="1.0,2.0;snappy,2.0;gzip"` could work? 🤔 And...

Alternative approach https://github.com/prometheus/prometheus/pull/13968

Thanks! We already started and it's tricky even with a lot of context, plus we still discuss details, so we will take it, but feel free to check other remote...

I don't have opinion on moving packages, I recall one discussion if owners of OTel contrib would like to "donate" this lib to us and how maintainership would work for...

(Hello from bug scrub meeting). Friendly ping @machine424 if you want to review, but it feels that: * This code is very much a critical path, so we have to...