I need the wisdom and experience of the crowd here:
We have a site which hosts many digital applications. In many cases the end user is experiencing an "application" error - meaning there cold be that no error has been raised on the server. these errors can either be identified by accessing some custom error pages or by seeing some text on the end user page.
The requirement: list all situations where this has happened with information about the end user (i.e. using USQL).
1.how do we identify these situations?
2. can USQL support this query ?
Answer by Julius L. ·
I think the best approach would be to raise these errors by using dtrum API (dtrum.reportError / dtrum.reportCustomError). However, this involves changes in the application code (just call the dtrum api when the error happens for the user) and might not be easy or suitable in your situation.
If this is not applicable in your situation, then if your application redirects the user to an error page, it might be possible to catch this as a user action (Load action probably in this case) and this should be visible in the user session.
Application errors that are just displayed for the user as regular text on the page are more difficult to catch. At the moment you don't have any other options than capture this text by defining a user action property that will capture this text. Probably by using a CSS selector or a server-side request attribute. Typically those errors would be displayed in an element having a class indicating this is an error message, so CSS is probably suitable.
And yes, USQL supports querying sessions having such aspects.