Description of the limitation and why it is relevant to address
As a developer I want to not only see that an error has occurred on a specific compute event, but also what the error was. This would help me to improve the app, even when users do not report their errors.
I think this is relevant for the VIKTOR platform because it will help developers improve their applications, which will result in a better experience for users.
Submitter proposed design (optional)
Add links of the stacktrace to EDITOR.COMPUTE events where an error occurred.
Current workarounds
Contact the user that experienced an error, and ask if they can recall what they did, and try to replicate this, and then report the error.
More context
This is related to an application that monitors the health of apps and the environment. An overview of the errors that occur over time are plotted, but this only shows which endpoints get errors, and not what the errors specifically are.