Ran into an issue where we are not capturing 503's via the UEM agent for an auth widget that gets loaded. UEM treats the call as 3rd party. However, we had a situation where the service gateway serving the authentication endpoint was down. In reviewing the data, these errors are not captured.
Is there a way to capture the 503's seen in the browser with the UEM agent? I have not found a way to do this.
Answer by Colin F. ·
Any update on the progress with being able to do this? We make several 3rd party calls, one of them is actually for login. We would really like to be able to capture/alarm on when there is an auth problem with the real user session. We do have this coverage from a synthetic perspective, but extending it to real-user is a definite priority.