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
Describe the solution you'd like
It would be really awesome to be able to use the RulesBasedSampler as a sub-sampler of a Rule in the parent RulesBasedSampler. Something like this:
Samplers:
__default__:
RulesBasedSampler:
- Name: Dealing with ErrorsConditions:
- Field: errorOperator: existsSampler:
RulesBasedSampler:
- Name: Ignore Errors From X ServiceConditions:
- Field: service.name
- Operator: =
- Value: service-xDrop: true
- Name: All the important errorsSampler:
EMADynamicSampler:
GoalSampleRate: 3FieldList:
- exception.type
- error.message
Describe alternatives you've considered
We could probably also do something similar by allowing rules to have layered conditions, where some can be scoped to span and some to the trace, and then also allowing for OR conditioning rather than the AND conditioning we do.
Additional context
Haven't heard this from customers really, but was an interesting thought I had that sprung from some questions I'd received.
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
It would be really awesome to be able to use the RulesBasedSampler as a sub-sampler of a Rule in the parent RulesBasedSampler. Something like this:
Describe alternatives you've considered
We could probably also do something similar by allowing rules to have layered conditions, where some can be scoped to span and some to the trace, and then also allowing for OR conditioning rather than the AND conditioning we do.
Additional context
Haven't heard this from customers really, but was an interesting thought I had that sprung from some questions I'd received.
The text was updated successfully, but these errors were encountered: