Nick Pillitteri

The CHANGELOG has just been cut to prepare for the next Mimir release. Please rebase `main` and eventually move the CHANGELOG entry added / updated in this PR to the...

The CHANGELOG has just been cut to prepare for the next Mimir release. Please rebase `main` and eventually move the CHANGELOG entry added / updated in this PR to the...

> * the querier sends a `TriggerBlockLoad([]ULID) map[ULID]bool` (naming suggestions welcome) RPC to each of the 3 store-gateways concurrently Maybe we could move this up a level to make a...

2.12 has been released. We should be good to close this, right?

The Prometheus TSDB code drops exemplars with no labels which is why Mimir rejects them on ingest. It wasn't a problem in practice until now because Prometheus never sends exemplars...

Discussion here when some of the logic to reject empty exemplars was added: https://github.com/grafana/mimir/pull/873

Sounds like negative caching for the results cache in the query-frontend.

Cadence has a [buffered backend](https://github.com/56quarters/cadence/blob/37d7d18d72f10646bec02d19197528ade03fcbe8/cadence/src/sinks/udp.rs#L139-L164) that combines multiple metrics into a single UDP (or UNIX socket) write. Will this work for your use case?

Thanks for the explanation. That's part of why I use Prometheus metrics for things these days. This seems like it'd probably involve a pretty big re-architecture to Cadence and change...

I believe the `mimir_namespace_prefix` option is intended to fix the case where you have multiple clusters, each with their own Alloy setup, talking to a single central Mimir. In your...