-
Notifications
You must be signed in to change notification settings - Fork 205
feat: NET::HTTP semantic convention stability migration #1572
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
base: main
Are you sure you want to change the base?
feat: NET::HTTP semantic convention stability migration #1572
Conversation
...mentation/net_http/lib/opentelemetry/instrumentation/net/http/patches/dup/instrumentation.rb
Outdated
Show resolved
Hide resolved
if use_ssl? && proxy? | ||
span_name = 'CONNECT' | ||
span_kind = :client | ||
else | ||
span_name = 'connect' | ||
span_kind = :internal | ||
end |
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.
Same question here as on Excon: why is connect capitalized in one case and lowercase in the other?
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'm not sure, but it seems to be intentional. I'll see if I can dig up anything on this. Also discussed in #1569 (comment)
This PR is intended to assist in the transition from the old to new HTTP semantic conventions. Per the HTTP semantic convention stability migration spec, users should be able to set the environment variable
OTEL_SEMCONV_STABILITY_OPT_IN
to:http
to emit stable conventions onlyhttp/dup
to emit both old and the stable conventionsHTTP GET
is now justGET
- specSpecial note about NET::HTTP changes:
http.target
is split into two separate attributes,url.path
andurl.query
, under stable conventions. Unlike some other HTTP libraries, NET::HTTP reports these attributes as one path. Because of this, some additional work was done to to separate the path from the query in order to report them as separate attributes.The agent is required to maintain this bridge for 6 months and may drop the environment variable in the next major version and emit only the stable HTTP and networking conventions.
This approach was approved in #1547