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

Add instrumentation for quarkus-resteasy-reactive #8487

Merged
merged 3 commits into from
May 15, 2023

Conversation

laurit
Copy link
Contributor

@laurit laurit commented May 12, 2023

Resolves #8319
Implements updating span name and route based on the invoked jax-rs method. The implementation is similar to what we do for other jax-rs. frameworks. Testing deviates from our usual practice of testing the earliest supported version because making tests for old quarkus versions seems hard.

@laurit laurit requested a review from a team as a code owner May 12, 2023 20:15
public void updateServerSpanName(ResteasyReactiveRequestContext requestContext) {
Context context = Context.current();
String jaxRsName = calculateJaxRsName(requestContext);
HttpRouteHolder.updateHttpRoute(context, HttpRouteSource.NESTED_CONTROLLER, this, jaxRsName);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HttpRouteHolder has a variant where it simply accepts a String route; you can use it and skip implementing the "fake" HttpRouteGetter

Copy link
Member

@trask trask left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice 👍

@trask trask merged commit 7e38a35 into open-telemetry:main May 15, 2023
44 checks passed
@laurit laurit deleted the quarkus-resteasy-reactive branch July 6, 2023 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Quarkus reactive client + agent opentelemetry -> all APIs are under / instead of their path on dashboard
3 participants