-
Notifications
You must be signed in to change notification settings - Fork 870
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 HTTP server tests for non standard methods #9446
Add HTTP server tests for non standard methods #9446
Conversation
293bf8e
to
ba2afa8
Compare
...src/main/java/io/opentelemetry/instrumentation/testing/junit/http/HttpServerTestOptions.java
Outdated
Show resolved
Hide resolved
1f509fd
to
97d9602
Compare
97d9602
to
507ad2f
Compare
* Returns a new {@link HttpServerRouteBuilder} that can be used to configure the {@link | ||
* HttpServerRoute}. | ||
*/ | ||
public static <REQUEST> HttpServerRouteBuilder<REQUEST> builder( |
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.
I had to add a builder for the HttpServerRoute
as well, because it updates the span name.
I'm starting to think that this may be kind of cumbersome for the users, if you want to use custom knownMethods
you have to set it in 3 different builders. What if we had some Http(Server|Client)Semconv
class that has just one builder, and provides facrory methods for all the instrumenter parts? Just an idea for future PRs.
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.
it does seem really easy to miss that you need to set knownMethod in all 3 of those places...
Resolves #8951