-
-
Notifications
You must be signed in to change notification settings - Fork 520
feat: include otel as custom sampling contex #2683
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
Merged
Merged
+37
−1
Conversation
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
solnic
reviewed
Sep 3, 2025
Collaborator
solnic
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR - please rebase this first which should fix the build 😄
solnic
requested changes
Sep 3, 2025
sentry-opentelemetry/spec/sentry/opentelemetry/span_processor_spec.rb
Outdated
Show resolved
Hide resolved
Sentry's opentelemetry adapter does not do the greatest job in adapting the opentelemetry span to a semantically correct sentry span, nor does it expose the opentelemetry span in the context for sampling decisions. This PR adds a opentelemetry span as an additional custom sampling context so it can be used for sampling decisions. This gives clients more opportunity to use the entire context of the opentelemetry span for sampling decisions, and allows replicating sampling mechanisms as orignally suggested by the Sentry team via the "Sampling Function". https://docs.sentry.io/platforms/ruby/configuration/sampling/#setting-a-sampling-function
solnic
approved these changes
Nov 25, 2025
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
🚀 New features to boost your workflow:
|
Merged
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.
Sentry's OpenTelemetry (OTel) adapter does not do the greatest job in adapting the OTel span to a semantically correct sentry span, nor does it expose the OTel span in the context for sampling decisions. This PR adds a OTel span as an additional custom sampling context so it can be used for sampling decisions. This gives clients more opportunities to use the entire context of the OTel span for sampling decisions, and allows replicating sampling mechanisms as originally suggested by the Sentry team via the "Sampling Function".
https://docs.sentry.io/platforms/ruby/configuration/sampling/#setting-a-sampling-function
Thanks for your Pull Request 🎉
Please keep these instructions in mind so we can review it more efficiently:
Other Notes
closes #2684
closes RUBY-86