20 Jun 2019 06:52 PM - last edited on 27 Apr 2021 04:09 AM by MaciejNeumann
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.
There is no dimension errors available in this context.
You can do only
SELECT userId, totalErrorCount FROM usersession WHERE useraction.application='PCIB ' AND totalErrorCount > 0 ORDER BY totalErrorCount DESC
Does that mean the documentation is wrong then? the API docs for the UserSession model?
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.
Any chance to get these changes to Changelog or a blog post? It seems several important improvements happened under the hood with 180 and 182.
The blog post about these changes is already published here: https://www.dynatrace.com/news/blog/find-the-user-session-data-you-need-and-better-understand-custom...
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 🙂