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

Support for metrics and tracing in Javalin web framework #6115

Open
davidcurrie opened this issue May 28, 2022 · 5 comments
Open

Support for metrics and tracing in Javalin web framework #6115

davidcurrie opened this issue May 28, 2022 · 5 comments
Labels
contribution welcome Request makes sense, maintainers probably won't have time, contribution would be welcome enhancement New feature or request new instrumentation

Comments

@davidcurrie
Copy link

Is your feature request related to a problem? Please describe.
Support for Open Telemetry metrics and tracing in the Javalin web framework.

Describe the solution you'd like
To have automatic support for Open Telemetry metrics and tracing in Javalin.

Describe alternatives you've considered
No alternatives were considered.

Additional context
See discussion in javalin/javalin#523

@trask
Copy link
Member

trask commented Jun 2, 2022

hi @davidcurrie! if you are interested in working on this, check out writing-instrumentation.md, writing-instrumentation-module.md, and using-instrumenter-api.md

@laurit laurit added the contribution welcome Request makes sense, maintainers probably won't have time, contribution would be welcome label Jun 2, 2022
@PhilKes
Copy link
Contributor

PhilKes commented Feb 23, 2023

@davidcurrie I was taking a look at this and even though there is no explicit support for javalin, metrics and spans are already created with the otel-javaagent. From what I can see the current version javalin-2.0.3 uses jetty-11.0, which is already supported by OpenTelemetry.
I set up an example javalin project with a simple REST Api and using the current opentelemetry-javaagent.jar, and both Spans for incoming HTTP Request as well as http_server metrics were created.

So is this already resolved or what is the expectation for new instrumentation?

@trask trask added the needs author feedback Waiting for additional feedback from the author label Apr 2, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Apr 9, 2023

This has been automatically marked as stale because it has been marked as needing author feedback and has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.

@github-actions github-actions bot added the stale label Apr 9, 2023
@davidcurrie
Copy link
Author

Sorry - somehow missed the question back in Feb. From what I remember, the issue with Javalin was that it's implemented as a single servlet hanging off /* so that's the path that was showing up on all the Jetty-based metrics. Unfortunately, we've been unable to continue with OpenTelemetry due to OSGi issues so I can't comment further and understand if this issue just gets closed out.

@github-actions github-actions bot removed the needs author feedback Waiting for additional feedback from the author label Apr 11, 2023
@cyanff
Copy link

cyanff commented Apr 26, 2023

From what I remember, the issue with Javalin was that it's implemented as a single servlet hanging off /* so that's the path that was showing up on all the Jetty-based metrics

Yeah, getting official otel support to get finer metrics would be great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution welcome Request makes sense, maintainers probably won't have time, contribution would be welcome enhancement New feature or request new instrumentation
Projects
None yet
Development

No branches or pull requests

6 participants