Error discrepancy between Web Applications and Error Inspector

[jakubwolanin]

Under Web Applications, I’m trying to investigate JavaScript errors, but I’ve noticed that many of them are missing compared to what I see in Error Inspector. We are not sending any custom errors and are using the default configuration, as we are still exploring error monitoring.

Additionally, why don’t errors in Error Inspector have access to source maps, while errors in Web Applications do?

Should source maps for Error Inspector be uploaded via the REST API or I can somehow configure it?

[t_pawlak · Accepted solution]

Hi,
This behavior is expected, as these two views are based on different data models in Dynatrace.

Web Applications is part of RUM Classic and shows errors in the context of a selected classic web application and its classic error configuration. In that area, Dynatrace distinguishes request errors, custom errors, and JavaScript errors, and JavaScript errors are handled through the classic web app settings

Error Inspector, is New RUM. - here doc: Error Inspector 

It analyzes frontend errors from the user.events data model in Grail and, on the Explorer page, groups error instances across all monitored frontends unless you filter them down. Because of that, you should not expect a strict 1:1 match with the classic Web Applications view.

Because of this, you should not expect a strict 1:1 match between these two views.

Check, that you have the same timeframe, same application, same error type