Better server span name for Spring MVC, Grails, Wicket and Struts #2814
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The main change in this PR is adding a flag in
ServletSpanNaming
to prevent controller instrumentation from setting the SERVER span name more than once.Otherwise, when the servlet request is forwarded to an error controller, the error controller is overwriting the SERVER span name that was set by the controller that handled the request.
This PR only applies this change to Spring MVC, Grails, Wicket and Struts instrumentation initially. Will follow up with issue or PR to apply this change to the remaining.