-
Notifications
You must be signed in to change notification settings - Fork 156
Ensure every correlation ID is properly logged #1000
Copy link
Copy link
Open
Labels
P2Normal priority items, should be done after P1Normal priority items, should be done after P1SDK-ConsistencyItems that deal with consistency between all MSALsItems that deal with consistency between all MSALsSupportabilityFor issues related to improving the customer support experienceFor issues related to improving the customer support experienceconfidential-clientFor issues related to confidential client appsFor issues related to confidential client appspublic-clientFor questions/issues related to public client appsFor questions/issues related to public client apps
Metadata
Metadata
Assignees
Labels
P2Normal priority items, should be done after P1Normal priority items, should be done after P1SDK-ConsistencyItems that deal with consistency between all MSALsItems that deal with consistency between all MSALsSupportabilityFor issues related to improving the customer support experienceFor issues related to improving the customer support experienceconfidential-clientFor issues related to confidential client appsFor issues related to confidential client appspublic-clientFor questions/issues related to public client appsFor questions/issues related to public client apps
Correlation ID's are created on a per-request basis in
RequestContext, and optionally set at the application level as an alternative. Every request gets a correlation ID, and they are critical to connect client-side logs to server-side logs.Logging these correlation IDs has been mostly unchanged since the first version of MSAL Java, however customer issues have shown that there a gaps where correlation IDs are not properly logged in all failure cases.
We should audit how correlation IDs are logged, and ensure: