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

More JAX-RS context in instrumentation #305

Closed
jrogers opened this issue May 2, 2018 · 8 comments
Closed

More JAX-RS context in instrumentation #305

jrogers opened this issue May 2, 2018 · 8 comments
Assignees
Milestone

Comments

@jrogers
Copy link

jrogers commented May 2, 2018

More of a feature request, but could the class/method names of the invoked resource be added to the span/trace name, or in the attributes? It would provide helpful context.

@jrogers jrogers changed the title More JAX-RS context More JAX-RS context in instrumentation May 2, 2018
@jrogers
Copy link
Author

jrogers commented May 2, 2018

I could probably create a pull request for this if I get some time.

@tylerbenson
Copy link
Contributor

@jrogers Thanks for the suggestion. Would you mind including a screenshot of the UI, and/or some examples of before/after to help me understand better what you're asking for?

@jrogers
Copy link
Author

jrogers commented May 4, 2018

So I'm just comparing jax-rs to our ruby tracing. See screenshots attached. In the ruby traces for rails, the rack and rails traces both have the Api::DocumentsController#show in the trace name and in the attributes, which lets me easily know what the code path taken was, without knowing how the http path was routed. In JAX-RS land, you can get this from the ResourceInfo context in a filter for logging. Looking at the instrumentation, I assume this can really just be retrieved from the class and method names of where the Path annotation is. See screenshots attached, using 0.7.0 of java agent.

ruby_rails
ruby_rack
jaxrs

@tylerbenson
Copy link
Contributor

@jrogers thanks for the suggestion. Sorry for the delay in implementing it. Can you take a look at #435? I believe that should solve your problem. You can try it out by using the build from the PR:
https://7873-89221572-gh.circle-artifacts.com/0/home/circleci/dd-trace-java/libs/dd-java-agent-0.13.0-SNAPSHOT.jar

Any other feedback or suggestions?

@tylerbenson tylerbenson self-assigned this Aug 13, 2018
@tylerbenson tylerbenson added this to the 0.13.0 milestone Aug 13, 2018
@tylerbenson tylerbenson added type: enhancement inst: others All other instrumentations and removed tag: needs investigation Issues needing investigations labels Aug 13, 2018
@jrogers
Copy link
Author

jrogers commented Aug 23, 2018

Sorry I didn't get around to testing this, was working on a different project. I can try it out tomorrow.

@tylerbenson
Copy link
Contributor

I'm doing the release right now, so you should upgrade to 0.13.0 when it's out.

@jrogers
Copy link
Author

jrogers commented Sep 11, 2018

BTW, tried out 0.14.0, looks good.

@tylerbenson
Copy link
Contributor

Great, thanks for reporting back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants