Improve logging
Some clients have voiced their frustrations with finding it difficult to identify issues in the system. Please see the feedback below from one of the clients below.
* The Elmah instructions are great information and could potentially be helpful. Unfortunately, the log file is so massive that I am not able to navigate it in any meaningful way. Unless I am mistaken there are not any ways to filter the data. I have attempted to download the csv file but the page never returns any results.
* It would still be massively helpful if something like the datadog trace ID or the HTTP request ID was displayed on the customer-facing unhandled exception window so that we could tie it back to an error if the customer sends us a screenshot. The fact that there is ZERO information on that unhandled exception screen makes it completely useless.
* I just had a customer complain that they couldn't submit an order due to unhandled exceptions. We impersonated them and were able to submit it fine. I see numerous errors in the logs that seem tagged with that customer's email address but I have no idea which one was causing their actual problem. Or if their real problem was even logged.
* Another suggestion was to review the Spire logs but nothing there seems to pertain to this customer. The Spire logs have very limited details to attempt to determine what job the error came from.
Great news! Our team has enhanced Logging and improved the Unhandled Error popup. These enhancements were included in July-sts Release - 5.2.2607.394+sts and Aug-sts Release - 5.2.2608.613+sts
- (July) Added the authenticated user to Storefront application log entries. Administrators can now trace which user encountered an API error when troubleshooting.
- (August) Added a timestamp with a copy link to the storefront unhandled-error popup, so shoppers can quickly share the exact time an error occurred with site support for faster troubleshooting.
- (August) Added a Reference ID block to the storefront error modal that shows the Cloudflare Ray ID and Datadog Trace ID for a failed request, so shoppers can share these identifiers with support and speed up error investigation.