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
As I expect (using telemetrygen) I get 100 traces in (in this case) Jaeger:
telemetrygen traces --otlp-http --otlp-endpoint "172.18.0.6:4318" --child-spans 5 --otlp-insecure --status-code 1 --traces 100
For the following configuration I also expect 100 traces in Jaeger, but get only 1 (=1%). It seems that it only hits the probabilistic policy
telemetrygen traces --otlp-http --otlp-endpoint "172.18.0.6:4318" --child-spans 5 --otlp-insecure --status-code 0 --telemetry-attributes http.response.status_code=500 --traces 100
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Consider this configuration:
As I expect (using telemetrygen) I get 100 traces in (in this case) Jaeger:
telemetrygen traces --otlp-http --otlp-endpoint "172.18.0.6:4318" --child-spans 5 --otlp-insecure --status-code 1 --traces 100
For the following configuration I also expect 100 traces in Jaeger, but get only 1 (=1%). It seems that it only hits the probabilistic policy
telemetrygen traces --otlp-http --otlp-endpoint "172.18.0.6:4318" --child-spans 5 --otlp-insecure --status-code 0 --telemetry-attributes http.response.status_code=500 --traces 100
When I change the numeric_attribute policy to this, it works as expected:
I still don't understand why I have to set the max_value, considering how it is implemented in https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/tailsamplingprocessor/internal/sampling/numeric_tag_filter.go (line 26-28 has clear explanation)
Anyone an idea?
Beta Was this translation helpful? Give feedback.
All reactions