[RUM-15273] 🔊 Add telemetry for trackResourceHeaders#4492
Merged
Conversation
🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage (details) 🔗 Commit SHA: ac7366b | Docs | Datadog PR Page | Give us feedback! |
Contributor
Author
|
@codex review |
|
Codex Review: Didn't find any major issues. 🚀 ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Bundles Sizes Evolution
🚀 CPU Performance
🧠 Memory Performance
|
- Bump rum-events-format submodule for telemetry configuration schema - Regenerate telemetry and RUM event types - Map trackResourceHeaders init value to default_headers or custom for telemetry
4dbbe2e to
e6316c1
Compare
bcaudan
reviewed
Apr 21, 2026
thomas-lebeau
approved these changes
Apr 21, 2026
f6d1dfd to
ac7366b
Compare
bcaudan
approved these changes
Apr 21, 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 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
We want to track how customers configure
trackResourceHeaders(default preset vs custom array) to understand adoption patterns. This adds ause_track_resource_headersfield to the telemetry configuration event.Changes
rum-events-formatsubmodule for the newuse_track_resource_headerstelemetry configuration schema fieldgetTrackResourceHeadersTelemetryValuehelper that maps the init configuration value:trackResourceHeaders: true→"default_headers"trackResourceHeaders: [...](array) →"custom"undefined/false→ omitted from the telemetry eventserializeRumConfigurationTest instructions
sandbox/test-track-resource-headers-telemetry.html:use_track_resource_headers: "default_headers":To test the
customcase, change the init config totrackResourceHeaders: [{ name: 'x-custom' }], close the browser, clear intake, and repeat steps 3-4. Expected value:"custom".Clean up:
Checklist