-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Refactor tail-sampling processor #31580
Comments
cc @kentquirk |
Pinging code owners for processor/tailsampling: @jpkrohling. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Yes, AND, I also think that the binary keep/drop structure is a problem because it's not adequately composable if the probability of the decision matters to you. This proposal is related but I'm not sure yet if it actually applies. |
I'm interested in #31584 if we could have more info / context / expectation :P |
I think this is also relevant for the discussion: #25122 |
Related: #31498 |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Component(s)
processor/tailsampling
Is your feature request related to a problem? Please describe.
The tail-sampling processor has been there for a few years now, and despite being relatively popular, it hasn't changed much over the years besides adding new policies. There are a few things I always wanted to do but didn't have the time or motivation, and it would be a good idea to list them here in case we have volunteers to work on them.
Describe the solution you'd like
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: