Hey all… due to Security, we started hiding some details on certain types of error messages. Those messages might have previously displayed information that would be inappropriate to display to the user showing them too much information. Whenever this happens, we instead display a “Correlation ID”.
But we need to improve the way that System Admins, Tech Support, Professional Services, Partners, etc., look up that correlation ID to find the “actual message”…
Note that your comments HERE in this forum may not be seen by our developers, but the comments on the IDEA will be seen, as they are actively looking at this idea, and discussing it there. So, please comment on the idea itself. Thank you.
What are examples of errors that the user shouldn’t see that would “give them too much information”? Generally I feel these show up for unhandled exceptions at the service level. Ideally these would all hit an administrative error log that could be easily searched by an error code given from the user.
Additionally updating the message to not just say Correlation ID {GUID} but to provide direction for the user would be ideal. Ask them to provide that to their IT staff not just include it in the message.
That correlation ID should have a stack trace behind it too, ideally the call BpmContext.CallStack property that you folks keep “private” on us
Ope! That wasn't supposed to happen. We have sent a message to our team,
and we will investigate the problem. Reference this id when asking
about this event.
32422143
With proper telemetry, we should have most of the information already. Why ask the user to do anything?
I’ve seriously considered using GetRows on Menu to do usage telemetry with Sentry. I use it for mobile app telemetry but would work great for error tracking and mitigation as well.
