opentelemetry-java-instrumentation
opentelemetry-java-instrumentation copied to clipboard
Add code attributes to play mvc controller spans
Related to #7345
I know there are still discussions (here and here) around these conventions, but figured another example might help us continue to validate
Is this the right approach?
Is this the right approach?
👍
cc @SylvainJuge
I'd suggest the advice conversion work to be done in a different PR since the main problem with this PR is that the added code attribute isn't useful.
I'd suggest the advice conversion work to be done in a different PR since the main problem with this PR is that the added code attribute isn't useful.
I ended up just switching this PR to focus on the advice conversion. If it would be cleaner to close this one and open a fresh one, I'm happy to do that.
I ended up just switching this PR to focus on the advice conversion. If it would be cleaner to close this one and open a fresh one, I'm happy to do that.
Good idea, the scope of this PR is limited to play-2.4, there is also play-2.6 instrumentation that needs to be migrated, but this can be done in a separate PR.
there is a failure in play 2.6 tests https://scans.gradle.com/s/36fci3go5n3se