With the latest release of Dynatrace we’ve greatly enhanced our user action detail pages with their own look and feel that distinguishes them from application pages. User action detail pages are now more compact and provide quick access to all relevant data.
To access user action detail pages:
- Select Web applications from the Dynatrace menu.
- Select an application.
- Scroll down to the Top consumers section and click View full details.
- Select an action listed on the Top consumers page.
Once on a user action detail page, click areas of the summary infographic at the top of the page to navigate to detailed charts related to each summary metric, or type a string into the Filter user types field to view real-user or synthetic-monitoring specific data.
Contributors breakdown chart
When it comes to analyzing user actions, one of the main questions to address is on which tier is the most response time consumed? Was more time spent on the frontend (i.e., mainly the browser), the network, or the server? Now, as a complement to the existing Action duration contributors chart on each application page, we’ve added an always visible Contributor breakdown chart. This chart gives you a quick overview of time spent on the frontend, the network, and the server. For more detail, click the View resource impact in waterfall button to see which resources impact the action duration and Document interactive time milestone.
Key user actions
A typical web application has some user actions that are more important than others. Examples include login, checkout, and special landing pages. Other user actions may be very complex and have relatively long durations compared to other pages. Consider, for example, how complex an airfare search action on a travel website can be. Such business-critical user actions can be marked as “key” user actions (formally known as “high priority” user actions). For such key user actions you may want to define specific Apdex thresholds. While Dynatrace anomaly detection automatically detects performance degradations and increases in errors in all your user actions, it’s still a good idea to provide special handling for your key user actions. By defining a regular user action as a key user action, you get long-term historical trends and can specify an appropriate Apdex threshold for the action. Key user actions can be pinned to your dashboard for quick access and accessed via the Key actions tab for comparison with other actions.