Christian Simon

@korniltsev if you got a moment, would like to understand how you feel about this

Yes I do agree, esp. once we want to attach more information (OTEL spec) to the mapping we should be careful what belongs together or not.

I do think we can copy vast amounts of mimir's block lazy loading: https://grafana.com/docs/mimir/latest/references/architecture/binary-index-header/ https://github.com/grafana/mimir/tree/main/pkg/storegateway/indexheader There are some design documents, but they are internal only (sorry no GL employees): https://docs.google.com/document/d/1fFYJzYslSSui8Nswfkh6Ez1hKwRIHkqJTwMXb8v3zyk/edit#heading=h.e7syi5b4uppu...

Do you mind to share more details about your setup (version of helm chart/image version and helm `values.yaml`). Also related log messages you can see when this error happens.

There are a few in https://github.com/grafana/pyroscope/tree/main/operations/pyroscope/jsonnet/pyroscope-mixin/pyroscope-mixin/dashboard. It is fair to say they are not very detailed and tested. We have a more internally, but they are closely coupled into our...

An internal slack reference for more details for GL employees: https://raintank-corp.slack.com/archives/C04TRP742NN/p1709718028724059

> These are from an android commit: [d483eed](https://github.com/armbian/linux-rockchip/commit/d483eed85ffb9879b103cd8d6b3fae367fa6193e). What about reverting it? I imagined it would be harder to revert this, but I had not tried. Now used revert and...

I have hit this problem (on a non-dkms OS), it helped patching this symbol restriction in the 5.10 kernel: https://github.com/armbian/linux-rockchip/pull/142

Just rebase, a review would be appreciated

If you still experiencing those errors, it would be interesting how you configured the ingest to your cluster. If you can share some yamls for that and maybe the values.yaml...