We use analytics cookies.We use cookies to analyze site traffic and improve your experience.
Loading...
System Design Masterclass · Observability Monitoring
Free preview: the first 2 parts of this 9-part lesson.
Already bought the course? Sign in to read the whole lesson.
this lesson is part of
System Design Masterclass
Unlock this lesson and the 751 other paid lessons
$25 once, by PayPal
See the System Design courseread the rest of this lesson in
System Design Masterclass
Unlock this lesson and the 751 other paid lessons
$25 once, by PayPal
See the System Design coursein Observability Monitoring
This lesson is part of the full System Design Masterclass. Unlock it along with 769 other lessons for a one-time payment.
One-time payment by card or PayPal
Get Lifetime AccessOne-time payment: UPI, card or netbanking
Get Lifetime Access18 Foundation lessons are free, no payment needed. Try them now
It is easy and good
“It is really nice and good Please join the course”
Your boss asks: "Are our users happy with the site's performance?" You could show them a P50/P95/P99 chart. Their eyes would glaze over. Percentiles are powerful but not intuitive to non-engineers.
Apdex (Application Performance Index) converts response time data into a single number between 0 and 1 that even a CEO can understand. 1.0 means everyone is happy. 0 means nobody is happy. 0.94 means "94% of users are satisfied."
It was designed by an industry consortium specifically to bridge the gap between engineering metrics and business communication. When you say "our Apdex dropped from 0.95 to 0.78 this week," leadership immediately understands that user satisfaction has degraded, no percentile interpretation required.
Apdex requires a single input: your threshold T, the response time you consider "satisfying" for the user. Once T is defined, every request falls into one of three buckets:
| Category | Response Time | Weight |
|---|---|---|
| Satisfied | <= T | 1.0 |
| Tolerating | > T and <= 4T | 0.5 |
| Frustrated | > 4T | 0.0 |
Formula: Apdex = (Satisfied + 0.5 * Tolerating) / Total Requests
Example with T = 500ms and 1000 requests:
Apdex = (800 + 0.5 * 150) / 1000 = 875 / 1000 = 0.875
| Apdex Range | Rating | Interpretation |
|---|---|---|
| 0.94 - 1.00 | Excellent | Users are delighted |
| 0.85 - 0.93 | Good | Most users are satisfied |
| 0.70 - 0.84 | Fair | Some users are frustrated |
| 0.50 - 0.69 | Poor | Many users are frustrated |
| < 0.50 | Unacceptable | Most users are having a bad time |