Skip to content

feat: seed root session ID for stable telemetry headers#54

Merged
khanayan123 merged 9 commits intomainfrom
ayan.khan/stable-session-id-headers
Apr 22, 2026
Merged

feat: seed root session ID for stable telemetry headers#54
khanayan123 merged 9 commits intomainfrom
ayan.khan/stable-session-id-headers

Conversation

@khanayan123
Copy link
Copy Markdown
Contributor

Summary

Seed root_session_id from the master-generated RuntimeID so all forked workers share the same root session ID for telemetry correlation.

Related

Set root_session_id from the RuntimeID generated in register_hooks
(master process) so all forked worker Tracers share the same root.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
@datadog-prod-us1-3
Copy link
Copy Markdown

datadog-prod-us1-3 Bot commented Apr 8, 2026

🎯 Code Coverage (details)
Patch Coverage: 100.00%
Overall Coverage: 51.40% (+0.15%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 99afdb1 | Docs | Datadog PR Page | Give us feedback!

Copy link
Copy Markdown
Contributor

@xlamorlette-datadog xlamorlette-datadog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
@khanayan123 khanayan123 marked this pull request as ready for review April 13, 2026 15:14
@khanayan123 khanayan123 requested a review from a team as a code owner April 13, 2026 15:14
@khanayan123 khanayan123 requested review from xlamorlette-datadog and removed request for a team April 13, 2026 15:14
@khanayan123
Copy link
Copy Markdown
Contributor Author

/merge

@gh-worker-devflow-routing-ef8351
Copy link
Copy Markdown

gh-worker-devflow-routing-ef8351 Bot commented Apr 14, 2026

View all feedbacks in Devflow UI.

2026-04-14 14:13:02 UTC ℹ️ Start processing command /merge


2026-04-14 14:13:09 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.


2026-04-14 14:15:11 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in main is approximately 7m (p90).


2026-04-14 14:22:41 UTCMergeQueue: The checks failed on this merge request

Tests failed on this commit 9f211e9:

What to do next?

  • Investigate the failures and when ready, re-add your pull request to the queue!
  • If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
  • Any question, go check the FAQ.

@khanayan123
Copy link
Copy Markdown
Contributor Author

/merge

@gh-worker-devflow-routing-ef8351
Copy link
Copy Markdown

gh-worker-devflow-routing-ef8351 Bot commented Apr 14, 2026

View all feedbacks in Devflow UI.

2026-04-14 14:23:53 UTC ℹ️ Start processing command /merge


2026-04-14 14:24:01 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in main is approximately 7m (p90).


2026-04-14 14:35:36 UTCMergeQueue: The checks failed on this merge request

Tests failed on this commit 54a5a8d:

What to do next?

  • Investigate the failures and when ready, re-add your pull request to the queue!
  • If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
  • Any question, go check the FAQ.

@khanayan123
Copy link
Copy Markdown
Contributor Author

/merge

@gh-worker-devflow-routing-ef8351
Copy link
Copy Markdown

gh-worker-devflow-routing-ef8351 Bot commented Apr 15, 2026

View all feedbacks in Devflow UI.

2026-04-15 16:38:03 UTC ℹ️ Start processing command /merge


2026-04-15 16:38:07 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in main is approximately 7m (p90).


2026-04-15 16:45:39 UTCMergeQueue: The checks failed on this merge request

Tests failed on this commit 374d9c8:

What to do next?

  • Investigate the failures and when ready, re-add your pull request to the queue!
  • If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
  • Any question, go check the FAQ.

Comment on lines 15 to +16
conf.runtime_id = runtime_id;
conf.root_session_id = runtime_id.string();
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

they share the same runtime id. is that expected?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, intentionally root_session_id is seeded from the master's RuntimeID before forking so all workers share it as a stable correlation key, even though each worker gets its own runtime_id at tracer construction time

khanayan123 and others added 4 commits April 21, 2026 11:14
ddapm-test-agent added vcr_json_body_normalizers as a required
kwarg on make_app(); the fixture was constructed without it, which
blew up the test-rum:amd64 / test-rum:arm64 GitLab jobs with:

  TypeError: make_app() missing 1 required positional argument:
  'vcr_json_body_normalizers'

Follow the existing vcr_* pattern and pass an empty string default.

Co-Authored-By: Claude Opus 4 (1M context) <[email protected]>
The GitHub Actions 'test' job installs from requirements.txt (pinned
to v1.40.0), while GitLab's test-rum job uses uv sync from
pyproject.toml (which pulls latest). The prior commit added the new
required kwarg vcr_json_body_normalizers to unblock GitLab, but
that then broke the GitHub job because v1.40.0 doesn't accept the
kwarg yet.

Unify both envs on v1.50.1, which introduced vcr_json_body_normalizers
in v1.47.0 (PR DataDog/dd-apm-test-agent#324, 2026-04-13).

Co-Authored-By: Claude Opus 4 (1M context) <[email protected]>
Picks up:
  - feat(c-binding): accept explicit span timestamps (#309)
  - unpin system-tests (back to @main) (#308)

Co-Authored-By: Claude Opus 4 (1M context) <[email protected]>
…ion-id-headers

# Conflicts:
#	requirements.txt
@khanayan123 khanayan123 merged commit 506ab6f into main Apr 22, 2026
5 checks passed
@khanayan123 khanayan123 deleted the ayan.khan/stable-session-id-headers branch April 22, 2026 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants