Let's imagine for a second that #1597 is resolved and we have a sampler that drops server spans based on the url. It is safe to assume that for any particular configured Otel SDK we still will need one more sampler, to decide the fate of all other spans. This is already a second example of "composite samplers", the first being existing ParentBased sampler.
This raises several questions:
- Should we formalise a notion of composite samplers in the spec?
- If yes, should we specify rules of composition? Delegation or list of samplers? Should they be combined as logical "and" or "or"? Short-circuit?
- Should env variable
OTEL_TRACES_SAMPLER be expanded to allow for configuration of sampler composition?
Let's imagine for a second that #1597 is resolved and we have a sampler that drops server spans based on the url. It is safe to assume that for any particular configured Otel SDK we still will need one more sampler, to decide the fate of all other spans. This is already a second example of "composite samplers", the first being existing ParentBased sampler.
This raises several questions:
OTEL_TRACES_SAMPLERbe expanded to allow for configuration of sampler composition?