Replies: 2 comments 1 reply
-
I somehow can't move this discussion. But it should be on collector-contrib, since it's about a contrib processor. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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