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
In the current header sampling mechanism, the samplingResult is depend on Instrumenter.start(), such as parent or traceIdRatio.
When the samplingResult create ends, there may be an invocation exception in instrument target method, and exception is usually the information we focus on. We want to be able to find this kind of focused span during the span process and then decide whether to sample it or not.
Of course, we can also realize our demands in the tail sampling mode, but it must be 100% sampled in the head, which will cause an increase in resource consumption to a certain extent.
So, can it support decide sample on proccess end ?
The text was updated successfully, but these errors were encountered:
The opentelemetry-java sampler operations are dictated by the specification, which currently only supports head based sampling. This issue requests extending samplers to allow them to be called at different stages in the span life cycle, which I believe is what you're asking for with supporting sampling when a span is completed: open-telemetry/opentelemetry-specification#307
In the current header sampling mechanism, the samplingResult is depend on Instrumenter.start(), such as parent or traceIdRatio.
When the samplingResult create ends, there may be an invocation exception in instrument target method, and exception is usually the information we focus on. We want to be able to find this kind of focused span during the span process and then decide whether to sample it or not.
Of course, we can also realize our demands in the tail sampling mode, but it must be 100% sampled in the head, which will cause an increase in resource consumption to a certain extent.
So, can it support decide sample on proccess end ?
The text was updated successfully, but these errors were encountered: