Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PROF-11412] Support correlating profiling with otel-api 1.5+ #4425

Merged
merged 4 commits into from
Feb 21, 2025

Conversation

ivoanjo
Copy link
Member

@ivoanjo ivoanjo commented Feb 21, 2025

What does this PR do?

This PR adds support for correlating profiling wih otel-api 1.5+.

Context storage was moved in open-telemetry/opentelemetry-ruby#1807 and we needed to update the profiler to account for this.

Motivation:

Keep profiling + otel correlation working.

Change log entry

Yes. Support correlating profiling with otel-api 1.5+

Additional Notes:

N/A

How to test the change?

In #4421 I had already bootstrapped the new appraisal groups needed for testing this. This PR enables them, and our existing test coverage will cover the new code path when used with otel-api 1.5+.

This will be used to access the OTEL context after
open-telemetry/opentelemetry-ruby#1807 .
**What does this PR do?**

This PR adds support for correlating profiling wih otel-api 1.5+.

Context storage was moved in
open-telemetry/opentelemetry-ruby#1807
and we needed to update the profiler to account for this.

**Motivation:**

Keep profiling + otel correlation working.

**Additional Notes:**

N/A

**How to test the change?**

In #4421 I had already bootstrapped the new appraisal groups needed
for testing this. This PR enables them, and our existing test
coverage will cover the new code path when used with otel-api 1.5+.
@ivoanjo ivoanjo added profiling Involves Datadog profiling otel OpenTelemetry-related changes labels Feb 21, 2025
@ivoanjo ivoanjo added this to the 2.11.0 milestone Feb 21, 2025
@ivoanjo ivoanjo requested review from a team as code owners February 21, 2025 11:25
@ivoanjo ivoanjo requested a review from AlexJF February 21, 2025 11:26
@pr-commenter
Copy link

pr-commenter bot commented Feb 21, 2025

Benchmarks

Benchmark execution time: 2025-02-21 11:48:08

Comparing candidate commit 16b8c46 in PR branch ivoanjo/prof-11412-otel-1_5-context-extraction with baseline commit 29a6bd8 in branch master.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 31 metrics, 2 unstable metrics.

Copy link
Contributor

@AlexJF AlexJF left a comment

Choose a reason for hiding this comment

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

LGTM!

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.72%. Comparing base (29a6bd8) to head (16b8c46).
Report is 5 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #4425   +/-   ##
=======================================
  Coverage   97.72%   97.72%           
=======================================
  Files        1365     1365           
  Lines       83337    83337           
  Branches     4219     4219           
=======================================
+ Hits        81440    81443    +3     
+ Misses       1897     1894    -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@datadog-datadog-prod-us1
Copy link
Contributor

Datadog Report

Branch report: ivoanjo/prof-11412-otel-1_5-context-extraction
Commit report: 16b8c46
Test service: dd-trace-rb

✅ 0 Failed, 20607 Passed, 1375 Skipped, 3m 9.05s Total Time

@ivoanjo ivoanjo merged commit 32c5d0b into master Feb 21, 2025
501 checks passed
@ivoanjo ivoanjo deleted the ivoanjo/prof-11412-otel-1_5-context-extraction branch February 21, 2025 11:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
otel OpenTelemetry-related changes profiling Involves Datadog profiling
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants