-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[routingprocessor] Instrument the routing processor with non-routed spans/metric points/log records counters (OTel SDK). #21476
[routingprocessor] Instrument the routing processor with non-routed spans/metric points/log records counters (OTel SDK). #21476
Conversation
dcfafb5
to
738c5c8
Compare
10f3c24
to
532e557
Compare
@jpkrohling can you please take a look at it? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, I just wanted to confirm whether we can use a sink tracer/logger/metrics provider, so that we can test the instrumentation.
"go.uber.org/zap" | ||
) | ||
|
||
var noopTelemetrySettings = component.TelemetrySettings{ | ||
TracerProvider: trace.NewNoopTracerProvider(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have a sink that we can use to test whether the data points are being created?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I couldn't find anything like that.
a888e1d
to
1da23ed
Compare
Description:
Instrument the routing processor with non-routed spans/metric points/log records counters (OTel SDK).
The routing entry key is used as a
routing_key
label for the metric. It is quite hard to use the value from routing entry as metrics label value, also for the case with OTTL it might simply not be possible. Also, in the future connector implementation of the routing processor we might use only OTTL routing statements.Link to tracking Issue:
Testing:
Documentation: