Skip to content
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

Merged
merged 1 commit into from
May 16, 2023

Conversation

kovrus
Copy link
Member

@kovrus kovrus commented May 3, 2023

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:

@github-actions github-actions bot added the processor/routing Routing processor label May 3, 2023
@github-actions github-actions bot requested a review from jpkrohling May 3, 2023 14:35
@kovrus kovrus force-pushed the routing-processor/instrument branch 2 times, most recently from dcfafb5 to 738c5c8 Compare May 3, 2023 17:53
@atoulme atoulme changed the title [rotuingprocessor] Instrument the routing processor with non-routed spans/metric points/log records counters (OTel SDK). [routingprocessor] Instrument the routing processor with non-routed spans/metric points/log records counters (OTel SDK). May 3, 2023
@kovrus kovrus force-pushed the routing-processor/instrument branch 2 times, most recently from 10f3c24 to 532e557 Compare May 4, 2023 08:02
@kovrus kovrus marked this pull request as ready for review May 4, 2023 08:02
@kovrus kovrus requested a review from a team as a code owner May 4, 2023 08:02
@kovrus kovrus requested a review from mar4uk May 4, 2023 08:02
@kovrus
Copy link
Member Author

kovrus commented May 5, 2023

@jpkrohling can you please take a look at it?

Copy link
Member

@jpkrohling jpkrohling left a 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(),
Copy link
Member

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?

Copy link
Member Author

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.

@kovrus kovrus force-pushed the routing-processor/instrument branch from a888e1d to 1da23ed Compare May 15, 2023 14:15
@jpkrohling jpkrohling merged commit 873e022 into open-telemetry:main May 16, 2023
@github-actions github-actions bot added this to the next release milestone May 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
processor/routing Routing processor
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants