Repository navigation
🔊 [RUM-18974] Report init context usage in telemetry configuration - #5277
Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 2 commits intoNov 17, 2026
Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 2 commits into
gh-worker-dd-mergequeue-cf854d[bot] merged 2 commits into
Conversation
Report whether the init context properties are provided when
initializing the SDK, as `init_context: { has_user, has_account }`
booleans, without sending their values.
Sync rum-events-format to get the new `init_context` field.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bundles Sizes Evolution
|
There was a problem hiding this comment.
More details
RUM and Logs configuration telemetry emit only boolean indicators for init-context user and account properties; customer values and unknown properties are excluded.
🤖 Bits Code Review · Commit c6b204b
🎉 All green!🧪 All tests passed 🎯 Code Coverage (details) 🔗 Commit SHA: e4c0fcf | Docs | View more details | Give us feedback! |
thomas-lebeau
approved these changes
Nov 17, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> # Conflicts: # package.json # yarn.lock
gh-worker-dd-mergequeue-cf854d
Bot
deleted the
grigory.gusarov/init-context-telemetry
branch
November 17, 2026 14:07
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Motivation
Follow-up of #5176, which added the
initContextparameter toinit()to set user and account information at initialization. As suggested in #5176 (comment), report its usage in the configuration telemetry, without leaking any customer data.The schema change is DataDog/rum-events-format#460.
Changes
rum-events-formatto the latestmaster(6c7c08f) to get the newinit_contextfield. This also brings unrelated upstream additions (track_ipc_resources,messageresource type,unrealsource,attach-element-stackusage feature).serializeInitContextinbrowser-core. It only reports whether each init context property is provided with a non-empty value, never the values:init_context: { has_user: true, has_account: false }. Unknown properties passed by JS customers are ignored.init_contextto the configuration telemetry sent by the RUM and Logs pre-start strategies.InitContextkey is serialized ashas_<snake_case_key>and exists in the telemetry schema (MapInitContextKey/ExtractTelemetryInitContext). Like the existingMapInitConfigurationKey/ExtractTelemetryConfiguration, these types are only used in tests, because template literal types aren't supported by TS 3.8. Open to moving the check to the source code if you prefer.Checklist
🤖 Generated with Claude Code