Cannot explore the most recent Loki log entries from Grafana
We recently lifted our loki from 2.6.2 stepwise to 2.9.8. Our deployment is “simple scalable mode” as container instances in Azure with Azure storage account blob container as storage.
With 2.6.2 we had 1x read and 3x writer. Now with 2.9.8 we have 2x read, 1x backend and 3x write.
We also switched from boltdb to tsdb.
Change Grafana Loki helm chart, but preserve existing logs
I’m trying to replace the loki-stack (2.10.2) with loki (6.5.2) helm-chart. For the new chart I used the same schemaConfig (same timeframe, index, schema etc) and the same S3 bucket. The new loki apparently does not see the logs that already exist. I was expecting loki to pick up the existing logs. What solutions do I have to make this work?