Replies: 1 comment 2 replies
-
Applying downsampling at service level means you end up with broken traces. We used to do that at Uber in the earlier versions of Jaeger, as a last ditch overload protection, but subsequently moved onto adaptive sampling that can achieve the same results by varying sampling rates in the entry services while keeping the sampled traces intact. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Seems current, the collector side only supports a global level down sampling. Is it possible to do service level down sampling configuration? This is to protect backend storage from misbehaved clients which sent a large number of traces causing logs of span drops.
Also ideally we should also be able to config a service level rate limit in addition to percentage-based downsampling to further protect backend storage.
Beta Was this translation helpful? Give feedback.
All reactions