Apdex tracks three response counts:
Satisfied: The response time is less than or equal to T.
Tolerating: The response time is greater than T and less than or equal to 4T. In this example, 4 x 1.2 = 4.8 seconds as the maximum tolerable response time.
Frustrated: The response time is greater than 4T.
Your configuration file's apdex_f value is four times your app server's Apdex T value. This threshold is useful, for example, with transaction traces. For more information, see the configuration file documentation for your New Relic agent.
The time calculation will change based on your own app's T setting. In the following example, T = 1.2 seconds.
| Level | Multiplier | Time (T Example = 1.2) |
|---|---|---|
| Satisfied | T or less | <= 1.2 seconds |
| Tolerated | >T, <= 4T | Between 1.2 and 4.8 seconds |
| Frustrated | > 4T | Greater than 4.8 seconds |
Apdex score
The Apdex score is a ratio value of the number of satisfied and tolerating requests to the total requests made. Each satisfied request counts as one request, while each tolerating request counts as half a satisfied request. An Apdex score varies from 0 to 1, with 0 as the worst possible score (100% of response times were Frustrated), and 1 as the best possible score (100% of response times were Satisfied).
The Apdex score is based on the ratio of satisfied and tolerating requests to the total requests made.
Example Apdex score:
During a 2 minute period a host handles 200 requests. The Apdex threshold T = 0.5 seconds (500ms). This value is arbitrary and is selected by the user.
- 170 of the requests were handled within 500ms, so they are classified as Satisfied.
- 20 of the requests were handled between 500ms and 2 seconds (2000 ms), so they are classified as Tolerating.
- The remaining 10 were not handled properly or took longer than 2 seconds, so they are classified as Frustrated.
The resulting Apdex score is 0.9: (170 + (20/2))/200 = 0.9.
參考地址
https://docs.newrelic.com/docs/apm/new-relic-apm/apdex/apdex-measure-user-satisfaction