Something as simple as ...
SELECT userId, totalErrorCount, errors FROM usersession WHERE useraction.application='PCIB' AND totalErrorCount > 0 ORDER BY totalErrorCount DESC
Returns that errors is an unknown field.
Solved! Go to Solution.
Maybe @Klaus E. / @Dominik P. can answer if there is something planned in recent versions.
The API doc lists the error as a nested object for each session which is true, but you need to query it as JSON to get that. With version 180 you will be able to use the usererror table and query for the same information as in the JSON.
Or what the name of the error is.
Oh, I forgot about that one (I've seen it already). Just in general, there are often changes in the DEM parts of Dynatrace that do not get it into the changelog or blog posts. For example, the new user action naming UI was like a blast for me - especially when some rules are difficult or impossible to write in the new UI.
I really appreciate the changes, especially about the errors - now being able to determine HTTP errors or custom errors. Kudos to the Dynatrace DEM team 🙂