You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Constructing URL objects is a bit costly (in addition to memory, it does a lot of validation), and we construct them in various http server and http client instrumentations, generally in order to populate http.url attribute. This could probably be optimized by adding some kind of "uri builder" to our api that can be used instead.
The text was updated successfully, but these errors were encountered:
I think the intent of the semantic conventions is to only return a URL if we have a URL, or otherwise return the parts, target, host, etc. Though not sure if this just makes it too confusing when writing instrumentation.
Constructing URL objects is a bit costly (in addition to memory, it does a lot of validation), and we construct them in various http server and http client instrumentations, generally in order to populate
http.url
attribute. This could probably be optimized by adding some kind of "uri builder" to our api that can be used instead.The text was updated successfully, but these errors were encountered: