Dynatrace relies on Apdex ratings to calculate the performance of—and thereby the likely user satisfaction with—each discrete user action. By default, the Apdex threshold for satisfactory performance of user actions, across all applications, is
Apdex ratings in Dynatrace are based on application-specific thresholds.
- An Apdex measurement rating of
1.0equates to Excellent performance.
- An Apdex rating above
0.85equates to Good performance.
- An Apdex rating below
0.7equates to Poor performance.
- Apdex ratings below
0.5are considered Unacceptable.
It’s recommended that you define appropriate timing thresholds for user satisfaction for each of the user actions that you watch in your application.
- Dynatrace Apdex ratings can be customized based on your specific requirements of your application. Once configured, they give you a quick and easy way of evaluating the performance of all user actions that you are monitoring: a value of 1 is perfect; values below 0.5 are poor.
- You can use Adpex ratings as benchmarks and compare two applications over time, even though the timing thresholds set up for the two applications may be different.
- Applications are typically comprised of many different user action types. For example, it might be acceptable to have a complex search in an application take up to 6 seconds to complete while the loading of the homepage in the same application might need to take less than 2 seconds to ensure user satisfaction. Such differences can be addressed by configuring different Apdex thresholds for these two different user action types.
For more details on the Apdex standard, see Apdex FAQs.
Configure Apdex settings
To configure your application's Apdex settings, including timing thresholds
- Go to Settings > Monitoring overview > Applications and select your application.
- On the application's overview page, click the (...) browse button and select Edit.
- Select the General tab to access Apdex configuration.
How errors and HTTP status codes affect Apdex
- XHR requests (XHR actions) with HTTP status codes
5xxare rated as Poor regardless of action duration.
- HTML requests (load actions) that can be correlated with web-request services that return HTTP status codes
5xxare also rated as Poor.