-
Notifications
You must be signed in to change notification settings - Fork 377
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
Allow tracing sampleRate smaller than 1% #5089
Comments
cc @zirain , we may have been trying to avoid using floats in the CRD in the past, but this is a legit use case, and recently the faultInjection API used floats gateway/api/v1alpha1/fault_injection.go Line 37 in dd1c66f
|
TBH, is that real meaningful in real world? |
gateway-api's mirroring filter introduced an additional |
With a lot of traffic, 1% is a ton of traces. A fraction would help because even with 0.01% is doesn't take long to find traces with errors or p99s worth looking into. |
you may not get help from traing with a very low sample rate, you may need CEL based sampler. |
Im just looking to sample a smaller percentage of all traffic, not do expressions. Success traces still have value to me too |
sgtm |
Description:
Envoy Gateway's
EnvoyProxy
CustomResourceDefinition expects the tracing field'ssampleRate
to be an integer, allowing 0 to 100.I'd like to keep tracing on, but sample perhaps 0.01% of traffic. This does not seem to be directly possible, although envoy-proxy itself seems to support float64 sample rates.
[optional Relevant Links:]
https://gateway.envoyproxy.io/latest/api/extension_types/#proxytelemetry
The text was updated successfully, but these errors were encountered: