-
Notifications
You must be signed in to change notification settings - Fork 851
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
Implement remotely configurable sampling for Jaeger exporter #796
Comments
@jkwatson @carlosalberto please provide more details in the description. |
Details to be found in open-telemetry/opentelemetry-specification#231 |
@pavolloffay Details are kinda spread that issue. Let me know what you think. |
Shouldn't this issue be entitled "Implement remotely configurable sampling" or something like that, and aim to provide a similar (i.e. functionally equivalent) mechanism as used in Jaeger - but applicable for any exporter used by the client? cc @yurishkuro |
The sampling strategy is served by collector gRPC endpoint. Here is the proto definition https://github.com/jaegertracing/jaeger-idl/blob/master/proto/api_v2/sampling.proto
|
I have started looking into this. In Jaeger this is implemented in this package https://github.com/jaegertracing/jaeger-client-java/tree/46798bdf199357afc535c98b8f6734b37090bf78/jaeger-core/src/main/java/io/jaegertracing/internal/samplers. It actually requires these classes: I am wondering whether it would be better to depend on @bogdandrutu any concerns on depending on |
My preference would be for OTel to be a clean cut, not to bundle Jaeger. Also, Jaeger sampling is upfront, I don't understand how it can be done in the exporter. |
It won't be in the exporter. It will be OTEL sampler implementation, we should decide whether it will be located in the same package as Jaeger exporter or a different one. |
details needed on what this entails....
The text was updated successfully, but these errors were encountered: