-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
False
-
None
-
False
-
Not Selected
-
1,000
-
0% To Do, 100% In Progress, 0% Done
-
1,000
-
3
-
100% (High)
-
3
-
1,000
Proposed title of this feature request
Tail based sampling for traces
What is the nature and description of the request?
Provide the ability to sample traces in a centralize point (e.g. the OTel collector) based on the transaction result or latency.
Why does the customer need this? (List the business requirements)
- As a customer, I'm not interested in storing all traces, as the majority of them are not relevant, if everything runs fine.
- It's important to document how our customers can decide to keep, for example, only 1% of traces coming from successful transactions and 100% of errors
- As an OpenShift user, I also want to store a percentage of traces having low latency and another percentage havinh high latency.
List any affected packages or components.
OpenTelemetry collector