-
Notifications
You must be signed in to change notification settings - Fork 283
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 priorities to resource names #3085
Conversation
...rap/src/main/java/datadog/trace/bootstrap/instrumentation/decorator/HttpServerDecorator.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense. Would be great to remove the getResourceNamePriority()
if it's not used anywhere.
bb1bacc
to
031bdd2
Compare
2799a8f
to
f905b64
Compare
@@ -151,6 +167,7 @@ class VertxHttpServerForkedTest extends HttpServerTest<Vertx> { | |||
} | |||
} | |||
|
|||
@Ignore("Route matching doesn't work with a handler before the controller") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a problem that seems to have already existed. It's going to require a large rework of the instrumentation in order to fix it. Essentially what happens is that every handler added to the router is instrumented, including things like auth handlers, which will usually have a mapping like /*
or null
but the way we have the instrumentation written only the first handler will evaluate the path as a route. In the case of this test the path is null because of router.route().handler(VertxChainingTestServer::firstHandler);
f905b64
to
db76665
Compare
db76665
to
e9e1ba4
Compare
Allows for resource name "types" to take precedence without having to worry about write order