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
HTTP client spans have no http.route attribute since client-side instrumentation is not generally aware of the "route", and therefore HTTP client spans SHOULD use {http.request.method}
Unfortunately, the spec keeps changing definitions in every version, which makes it hard to keep up. We need to upgrade soon.
Hello!
Is there a reason for not adding the
http.route
attribute to client spans name? I see it is not defined in the specification.In the implementation I see a "TODO" in this line.
Thank you
EDIT:
Just saw that there is an
url.template
attribute for client name here but is not implemented.The text was updated successfully, but these errors were encountered: