|The complete mobile delivery chain (Image Courtesy: Compuware)|
|"Clean room" environment allows quick isolation and correction of the APM issue (Image courtesy: Compuware)|
You still need to maintain the monitoring methodology from the end user perspective. Why? because all components making the experience come together in the browser/app. In mobile, typically there are more 3rd party vendors (which you need to watch!) compared to desktop.
So you ask yourself, should I include the wireless carrier in my monitoring, or monitor via a connected ethernet line? Here is my recommendation.
- When you're trying to identify, isolate and address issues, you want to perform operational monitoring over the ethernet (eliminate noise from the cellular link). Why?
- Most issues have to do with backend issues which you can correct, and those manifest themselves in the same way on wired connections (you can think of a wired connection as the equivalent of iPad on wifi).
- Issues related to cellular link performance are highly intermittent and you can't fix them (unless you're the carrier or someone the size of Google, and even then.).
- When you're trying to optimize the experience, understand the true end user experience, perform experiential monitoring (using real user experience data that includes the cellular and wifi links). Why?
- Because you can understand the end user experience globally and tune your CDN, composition of components on your page/app
- You can better identify trends and address those by dynamic tuning of the backend
Hope this helps, interested in your thoughts!