Semantic conventions for URL
This document defines semantic conventions that describe URL and its components.
|string||The URI scheme component identifying the used protocol.||Recommended|
|string||Absolute URL describing a network resource according to RFC3986 ||Recommended|
|string||The URI path component ||Recommended|
|string||The URI query component ||Recommended|
|string||The URI fragment component||Recommended|
: For network calls, URL usually has
scheme://host[:port][path][?query][#fragment] format, where the fragment is not transmitted over HTTP, but if it is known, it should be included nevertheless.
url.full MUST NOT contain credentials passed via URL in form of
https://username:email@example.com/. In such case username and password should be redacted and attribute’s value should be
url.full SHOULD capture the absolute URL when it is available (or can be reconstructed) and SHOULD NOT be validated or modified except for sanitizing purposes.
: When missing, the value is assumed to be
: Sensitive content provided in query string SHOULD be scrubbed when instrumentations can identify it.
Capturing URL and its components MAY impose security risk. User and password information, when they are provided in User Information subcomponent, MUST NOT be recorded.
Instrumentations that are aware of specific sensitive query string parameters MUST scrub their values before capturing
url.query attribute. For example, native instrumentation of a client library that passes credentials or user location in URL, must scrub corresponding properties.
Note: Applications and telemetry consumers should scrub sensitive information from URL attributes on collected telemetry. In systems unable to identify sensitive information, certain attribute values may be redacted entirely.