Closed jjbayer closed 1 week ago
I'd prefer if we had a generic system instead of adding more specific stuff. Now it's the
span.op
in the future it might bespan.foo
. This is close to being a system which can write attributes based on rules.
@Dav1dde I considered it, the question is always, where do we stop? This PR is already a generalization of the initial idea of slapping some hard coded rules onto span normalization. But I agree that I could at least make the target field (span.op
) part of the configuration, and make it independent of spans (the selector has $span...
in it anyway).
considered it, the question is always, where do we stop? This PR is already a generalization of the initial idea of slapping some hard coded rules onto span normalization.
Fair enough.
But I agree that I could at least make the target field (span.op) part of the configuration, and make it independent of spans (the selector has $span... in it anyway).
I'd like that, but that may require a Setter
trait.
Add global option that allows inferring the span op, with rules like this:
ref: https://github.com/getsentry/relay/issues/3637