You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The samplers offered by the OpenTelemetry Go SDK do not match this functionality. This means that an application cannot sample in the same way ; if an application could sample using the same algorithm using the same hash seed, it would allow application owners to ensure that the traces emitted by the application are not double sampled, therefore reducing the network traffic going to the collector.
Proposed Solution
I think the OpenTelemetry Go SDK could offer a sampler compatible with the collector's probabilistic sampler.
Alternatives
None found.
Prior Art
Current samplers can be reused somewhat to get this done. It might be best to use a separate sampler altogether to avoid breaking existing code.
Additional Context
The text was updated successfully, but these errors were encountered:
Problem Statement
The collector offers https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/probabilisticsamplerprocessor which allows users to sample traces efficiently.
Notably, it allows to choose the source of sampling, by default the trace id, and a hash seed that can be used to uniformly trace across many collectors scaled horizontally.
The samplers offered by the OpenTelemetry Go SDK do not match this functionality. This means that an application cannot sample in the same way ; if an application could sample using the same algorithm using the same hash seed, it would allow application owners to ensure that the traces emitted by the application are not double sampled, therefore reducing the network traffic going to the collector.
Proposed Solution
I think the OpenTelemetry Go SDK could offer a sampler compatible with the collector's probabilistic sampler.
Alternatives
None found.
Prior Art
Current samplers can be reused somewhat to get this done. It might be best to use a separate sampler altogether to avoid breaking existing code.
Additional Context
The text was updated successfully, but these errors were encountered: