jspc / gist:ae63f3a17de24492b9f08df0c5053fec

1. Actor queries loki for `app_name: my-website`, `2025-06-10T00:00:00 to 2025-06-11T00:00:00` 2. loki queries index store for `app_name: my-website, customer: dexory, range: [2025-06-10T00:00:00, 2025-06-11T00:00:00]` 3. index store returns logIDs `123`, `234`, `345`, `999` 4. loki queries cache and gets a hit on `123` 5. loki retrieves `234`, `345`, `999` from blob store 6. loki applies filters and transformations to `234`, `345`, `999` 7.1 loki returns `123`, `234`, `345`, `999` to actor 7.2 loki writes `234`, `345`, `999` to cache 8 cache writes `234`, errors because the payload isn't conformant, *doesn't remove erroneous addition* ---- step 6: this is where the stupid field thing happens. Consider: 1. Loki parses payload 2. Loki looks for dodgy key 3. If found, loki updates raw text (perhaps to make sure it doesn't accidentally create a non-conformant field), and this is where the stupid overwrite instead of insert comes in