fix(telemetry): drop undocumented ext.os.release / ext.app.initTs#642
Merged
Conversation
OneCollector rejected every batch with
`{"acc":0,"efi":{"InvalidEventFormat":"all"}}` because the envelope
carried two fields that aren't part of the documented CS 4.0
extension slots:
- ext.os.release (the documented ext.os keys are name, ver, bootId)
- ext.app.initTs (the documented ext.app keys are name, ver, id,
iid, expId, userId, sesId, env, asId, locale, tz)
A live probe against the production ingest confirmed the diagnosis:
removing either field flips a 400 back to acc:1; either field on its
own is enough to fail the whole batch.
`_resource_to_ext()` no longer maps these attributes, and
`_build_resource()` no longer puts them in the Resource. The
`_init_ts` instance attribute is dropped too (unused after the
mapping removal). Unit tests are updated to assert the trimmed
envelope, plus a regression test that fails fast if anyone
re-introduces either mapping.
Closes #635
xieofxie
approved these changes
May 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #635.
Diagnosis
The OneCollector backend rejected every batch with
{"acc":0,"efi":{"InvalidEventFormat":"all"}}. A live probe againstthe production ingest narrowed the cause to two fields in the
envelope that are not part of the documented CS 4.0 extension
slots — either field on its own is enough to flip the whole batch
from
acc:1toInvalidEventFormat: all:ext.os.releaseext.oskeys:name,ver,bootId)ext.app.initTsext.appkeys:name,ver,id,iid,expId,userId,sesId,env,asId,locale,tz)ext.app.initTsis rejected for every value type (float, int, ISO8601 string), so this is the field name being unknown to the
schema, not a type mismatch.
The previous
acc:1validation in #456 happened to use a minimalenvelope (no
ext), so the bad fields never reached the wire. Theexisting unit tests asserted the envelope shape but never validated
it against the live backend, so the regression slipped through.
Fix
_resource_to_ext()no longer mapsos.release → ext.os.releaseor
initTs → ext.app.initTs._build_resource()no longer puts those attributes in theResource at all; the
_init_tsinstance attribute is dropped too(it was only read by the now-removed mapping).
the trimmed envelope, plus a new
test_export_omits_undocumented_cs40_ext_fieldsfails fast if anyone re-introduces either mapping.
Probe log (production ingest, masked)