-
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
Support for Jaeger remote sampler #327
Support for Jaeger remote sampler #327
Comments
@lizthegrey Do you have thoughts on this, given your OTEP about sampling? |
Since this is just a proxy in Jaeger does it make sense to configure and handle this entirely in the receiver? If we can agree on how to handle this I would be glad to add the feature as we need it internally to start using the otel collector. |
We discussed about the collector integration to use extensions. |
I will pick this up. @bogdandrutu - should this issue be moved to otel-col repo? |
move to collector repo |
I suspect there is a desire to apply sampling in the client-side SDK, in which case this issue belongs here. |
Yes, once jaeger remote sampling is implemented in the agent/collector, we can pick up the client side SDK sampling. |
The remote sampler will consult Jaeger agent for the appropriate sampling strategy to use. This allows controlling the sampling strategies in the services from a central configuration in Jaeger backend, or even dynamically.
The text was updated successfully, but these errors were encountered: