Skip to content

chore: remove experimental_propagate_process_tags_enabled from runtime metrics initialize#5465

Draft
wantsui wants to merge 18 commits intomasterfrom
refactor-runtime-metrics-chore
Draft

chore: remove experimental_propagate_process_tags_enabled from runtime metrics initialize#5465
wantsui wants to merge 18 commits intomasterfrom
refactor-runtime-metrics-chore

Conversation

@wantsui
Copy link
Copy Markdown
Collaborator

@wantsui wantsui commented Mar 16, 2026

What does this PR do?

Follows up on #5432 (comment) and gets rid of the propagate_process_tags_enabled usage in runtime_metrics.rb

Motivation:

Change log entry

No.

Additional Notes:

How to test the change?

wantsui and others added 18 commits March 9, 2026 18:52
…tags are disabled to avoid mixing testing concerns
Co-authored-by: Munir Abdinur <munir.abdinur@datadoghq.com>
… include experimental and adjust specs to match
@github-actions github-actions bot added the core Involves Datadog core libraries label Mar 16, 2026
@wantsui wantsui added the AI Generated Largely based on code generated by an AI or LLM. This label is the same across all dd-trace-* repos label Mar 16, 2026
Comment on lines 25 to +27
Core::Runtime::Metrics.new(
logger: options[:logger],
telemetry: telemetry,
experimental_propagate_process_tags_enabled: options.fetch(:propagate_process_tags_enabled) do
options.fetch(:experimental_propagate_process_tags_enabled)
end
telemetry: telemetry
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Wait, my suggestion was to get rid of this whole default, not just passing the flag to Core::Runtime::Metrics.new 👀

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

🤔 I'll keep refactoring (and now I'm glad I split this out into its own PR).

Base automatically changed from enable-process-tags to master March 17, 2026 13:58
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Is this change intended for this PR?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

No but it's weird it's showing up here when the PR where this branch split from has it already: https://github.com/DataDog/dd-trace-rb/pull/5432/changes#diff-aad6bdf47cba29fa1524d045aeff4a4f02d53882030f72b3669fda0bc969b8c7

I'll dig into it!

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

It's because this PR is/was stacked atop #5432 but that got squash-merged to master, so git doesn't recognize they are the same.

So this needs a rebase atop master. I suspect won't detect the commits as the same/empty, so you may need to manually do an interactive rebase and remove those commits from the list.

(There's a non-zero chance that claude also can do it for you if you give him the info from above :P )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AI Generated Largely based on code generated by an AI or LLM. This label is the same across all dd-trace-* repos core Involves Datadog core libraries

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants