-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Rename ParentOrElse sampler to ParentBased and enhance it according to the spec #1153
Conversation
- Renaming of type and sampler function - Enhancing ParentBased with sampler options - Set default samplers for each applicable parent-based case - Adjust ShouldSample(...) func accordingly
- add tests for ParentBased sampler options and description - renaming in trace_test.go
Codecov Report
@@ Coverage Diff @@
## master #1153 +/- ##
========================================
+ Coverage 77.7% 77.9% +0.2%
========================================
Files 135 135
Lines 7153 7191 +38
========================================
+ Hits 5559 5603 +44
+ Misses 1350 1344 -6
Partials 244 244
|
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.
Looks like the correct approach. Only issue is the configuration format.
- More clearer naming of structs; add comments where missing - Adhere to the configuration style guide
Thanks for the feedback, I reworked the configuration so that it adheres to the styling guide, hopefully now all is A-OK. |
Update the examples to use the current API for configuring production sampling. These names were changed a couple of years ago. open-telemetry/opentelemetry-go#1115 open-telemetry/opentelemetry-go#1153
Relevant specification change from open-telemetry/opentelemetry-specification#610
More specifically, the changes include:
ParentOrElse
sampler toParentBased
fallback
sampler renamed toroot
remoteParentSampled
,remoteParentNotSampled
,localParentSampled
,localParentNotSampled
); if not set, appropriate defaults are used in accordance with the specResolves #1084