Since we released Apdex in April, we’ve been tossing around ideas to improve and extend our support of Apdex. You might have noticed that last week we introduced a few big changes:
- “Synthetic Apdex” — separate Apdex scoring for AppView monitoring performance, to better compare synthetic vs RUM experience
- Experience filters — easy drill down on requests with are failed, tolerating, or satisfied experiences to understand what made performance bad for those users
- 500s as fails — if a request returned a 50x error code to the user, they probably had a bad experience. This automatically fails an request in Apdex scoring now, regardless of latency.
- Worldwide Apdex — you can view Apdex performance by geographic region
Here’s a bit more on a few of those.
Using AppView for synthetic monitoring of your app? You could always compare latency between real and synthetic users to understand differences and drill down, but what about the “experience” of it? Now it’s possible to compare synthetic and RUM data in TraceView–and later this month, it will be built in to AppView directly as well.
What’s making these requests be so slow they’re ruining the user experience? Now there’s a one-click drill down to isolate problematic outliers and solve the most pernicious end-user problems.
What were the requests that caused my API score to bottom out?
The geographic map on the end-user view is now scored by Apdex instead of absolute latency–this means you can understand the end-user experience on a region-by-region basis.
Not using Apdex or Transaction Groups yet? Log in and get started today!