Under the hood
Useful1 Signal2
Failed telemetry batches can be stored and retried differently, but only with a backend that nothing here supplies.
A stream-based retry path for telemetry batches exists but is inert unless a v5 storage backend is passed in.
What's wrong with this entry?
Anonymous. No account, no email.
What
The first-party event exporter gained a path that stores failed-event batches as append-only v5 streams keyed by run id and retries earlier runs in the background.
Details
- Leftover flat JSON batches are migrated into streams using deterministic record ids of the form
flat-migration.<index>.<hash>, and the flat file is deleted afterwards. - Only taken when a storageV5 backend is passed to the exporter; what enables that backend could not be determined.
- Without a v5 backend the existing flat-file path is unchanged.
Evidence
1P event logging: failed to persist failed-event queue to v5 stream
Strings lifted out of the shipped bundle, so the claim above can be checked against them.