Christian Haudum

Could someone facing this issue post logs (from `indexgateway` or `backend` or `all` target) here, even if they seem to be irrelevant? Also to verify, this happens both with `boltdb-shipper`...

As a workaround, you can set the per-tenant setting `query_ready_index_num_days` ([docs](https://grafana.com/docs/loki/latest/configure/#limits_config)) to a value greater than `0` (default value), e.g. to `1`. Note that this will pre-fetch index data to...

> I think the issue should be renamed, because it does not occur on S3 only. Agree. Will rename the issue.

Good news, [Loki 2.9.1](https://github.com/grafana/loki/releases/tag/v2.9.1) has been released.

~~@alex-berger Please report this issue to the [Grafana Alloy](https://github.com/grafana/alloy) repository.~~

Sorry, I came here from an issue in Loki, and was under the impression that I was looking at an issue in the Grafana/Loki repository.

In the case of CrateDB Cloud we need to bootstrap multiple users. Them being bootstrapped by CrateDB itself would be great. I thought, instead of having a single environment variable...

Hey @zarbis thanks for trying out the experimental bloom filter feature and reporting the issue. Did you see any restarts of the bloom-planner component while the builder processed the task?...

Hi @diranged Did you run Loki using the vanilla Helm chart? I got a different panic, see https://github.com/grafana/loki/pull/14110 but could not reproduce the duplicate metrics registration.

I am able to reproduce this state now. Loki built from `main` does not have this issue, so needs to be fixed on the `release-3.1.x` branch only.