What is an Apdex rating?

Apdex is a universal standard that is used to measure user satisfaction with application performance. 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 all user actions across all applications is 3 seconds. It is recommended however that you define your own timing thresholds for user satisfaction for each of the user actions that you watch in your application.

Benefits of Apdex ratings

  • 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.

Configure Apdex settings

To configure your application’s Apdex settings, including timing thresholds, go to Settings > Monitoring overview > Applications and select your application. Then go to User actions.

How errors and HTTP status codes affect Apdex

  • User actions with JavaScript errors are rated as Poor. It can happen that your user actions are in fact fast and below the Apdex threshold, but they are colored red and rated as Poor nonetheless because many of the user actions have JavaScript errors.
  • XHR requests (XHR actions) with HTTP status codes 4xx or 5xx are rated as Poor regardless of action duration.
  • HTML requests (load actions) that can be correlated with web-request services that return HTTP status codes 4xx or 5xx are also rated as Poor.