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
Tracing of requests across systems typically relies on HTTP headers to establish correlation ids.
There's https://www.w3.org/TR/trace-context/ which is seeing adoption but Microsoft historically also uses x-ms-client-request-id and x-ms-request-id.
For compatibility, we can start with x-ms-request-id/x-ms-client-request-id and include those in log messages. Later on we can add W3C Trace Context headers and eventually deprecate and then remove the x-ms-* headers.
The text was updated successfully, but these errors were encountered:
Tracing of requests across systems typically relies on HTTP headers to establish correlation ids.
There's https://www.w3.org/TR/trace-context/ which is seeing adoption but Microsoft historically also uses
x-ms-client-request-id
andx-ms-request-id
.For compatibility, we can start with
x-ms-request-id
/x-ms-client-request-id
and include those in log messages. Later on we can add W3C Trace Context headers and eventually deprecate and then remove thex-ms-*
headers.The text was updated successfully, but these errors were encountered: