Bartlomiej Plotka

We are on the same page, there are ways to kill fork. Let's discuss it here: https://github.com/thanos-io/thanos/issues/5393

I updated fork, so we can start using IMDSv2 unless there is anything to do on our side to enable it. See: https://github.com/thanos-io/thanos/pull/5474

Yea we could now safely drop the rule of uploading only blocks with compaction level 0, however, I am just curious, is there any use case or reason why anyone...

@V3ckt0r let's move this discussion to the https://github.com/improbable-eng/thanos/pull/207 PR then. I think you cannot see these uploads because thanos marked these as "uploaded" in `thanos.shipper.json` (because they were level compaction...

Seems to work for @V3ckt0r

hm just rethinking... @V3ckt0r > @Bplotka in regards to your question about local tsdb compaction. I'm guessing those who are not using an object store would still want local compaction,...

OK new approach emerged: In v2.2.1 we added min-block-size compaction delay to prometheus. This will help in 99% cases to avoid conflicts between thanos hardlink before upload & prometheus local...

As @TimSimmons mentioned, we should add more info in docs as well, how to configure Prometheus for the best experience.

Sorry for delay @mattbostock! Regarding mentioned benefits: > Reduces the load on the global compactor in Thanos, thus reducing requests/bandwidth on the object storage. True, but not sure if req/band...

Cool, I see the disaster recovery goal for some users, but not sure if Prometheus scraper should be treated as a backup solution to your on-premise/cloud/magic object storage. There must...