Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Status Gathering interest
Categories Misc.
Created by Guest
Created on Sep 19, 2024

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.

  • Optimizely
    Sara Winter
    Reply
    |
    Sep 26, 2024

    Thank you for submitting this request! We have added this item to our backlog for future consideration and prioritization.