RUM-14563 Add header capture configuration API and HeaderProcessor#2699
Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 3 commits intoMar 2, 2026
Conversation
barboraplasovska
force-pushed
the
bplasovska/RUM-14563/header-capture-api
branch
3 times, most recently
from
February 17, 2026 15:30
32442e6 to
9c6814a
Compare
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🔗 Commit SHA: 5b2ceec | Docs | Datadog PR Page | Was this helpful? React with 👍/👎 or give us feedback! |
5 tasks
barboraplasovska
force-pushed
the
bplasovska/RUM-14563/header-capture-api
branch
from
February 18, 2026 09:31
9c6814a to
7638924
Compare
barboraplasovska
marked this pull request as ready for review
February 18, 2026 13:16
mariedm
reviewed
Feb 19, 2026
mariedm
left a comment
Member
There was a problem hiding this comment.
Looks great! 👌
I believe this PR should add an entry to the changelog since it's introducing a new customer-facing option. Also, given that it's public but not yet wired to the resource pipeline, it should be merged to a feature branch instead of develop.
barboraplasovska
changed the base branch from
develop
to
feature/header-capture
February 20, 2026 14:45
barboraplasovska
force-pushed
the
bplasovska/RUM-14563/header-capture-api
branch
from
February 20, 2026 14:48
6f88d3f to
05820dd
Compare
5 tasks
mariedm
reviewed
Feb 26, 2026
Contributor
Author
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
gh-worker-dd-mergequeue-cf854d
Bot
merged commit Mar 2, 2026
1349091
into
feature/header-capture
18 checks passed
gh-worker-dd-mergequeue-cf854d
Bot
deleted the
bplasovska/RUM-14563/header-capture-api
branch
March 2, 2026 09:41
3 tasks
5 tasks
Merged
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.
What and why?
This is the first PR for Network Header Capture. It adds the public configuration API (
TrackResourceHeaders,HeaderCaptureRule) onURLSessionTrackingto let users opt into capturing HTTP request and response headers on RUM resources. It also introducesHeaderProcessor, which resolves the capture list from configuration rules, applies security filtering (regex-based sensitive header detection, reserved iOS headers exclusion), and enforces size limits. RUM models are regenerated to includerequest.headersandresponse.headersonRUMResourceEvent.Follow-up PR will wire the processor into the resource interception pipeline.
Review checklist
make api-surfacewhen adding new APIs