Best practices for staying aware of application failures?

Discussion created by evtguy on Feb 14, 2013
Latest reply on Feb 19, 2013 by evtguy
This is more of an open ended discussion and general question-

As I debug my application more and get it ready for deployment, I've thought more about the post-development phase of an application and one large question has been looming- how do you stay informed about when your app fails? One situation that comes to mind is when the map services you are utilizing in your map are not available.

For example, yesterday and into this morning, I noticed that the layers in my app weren't loading correctly and that the JSON requests were timing out. As it turns out, our Server ran out of disk space. Since I'm actively developing and debugging I can take action fairly quickly; once we publish, however, how do I get timely indications of problems without having to constantly monitor its performance manually (or worse yet get informed by a user)?