Replies: 1 comment 3 replies
-
It is actually explained in semantic conventions: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md#http-server-semantic-conventions Do you find that explanation confusing? How can we make it more clear? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Just wanted to share, if you are an instrumentation author, or aspire to be one, the route() method may confuse you. I think I finally understand the purpose of the route() method in the instrumenter API for HttpAttributesExtractor
When implemented on a server side, it makes sense to me, client-side it does not make sense to me (yet). See the Jaeger viewer image below, I used the Armeria server 1.9.x and set up a simple service in armeria listening to the path /greet{:name}. The route was picked up from the internal logical paths that the armeria responded to the request with.
Beta Was this translation helpful? Give feedback.
All reactions