Uptime status is only fully reflected in systems that measure activity on both sides –the server side and the user side. Paessler AG’s suite of network monitoring solutions equips software companies to do just that – managing network availability, performance and usage efficiently. It accomplishes this through remote probes, differentiated sensor types, and push notifications.
Remote probes allow you to monitor diverse networks, for instance subsidiaries, independent networks within your company, and most importantly your customers’ networks. This allows you to determine with greater accuracy whether your end users are experiencing performance issues or not and if so, precisely where the source of the issue resides.
With over 200 sensor types available “out of the box” and the ability to monitor as many as 20,000 sensors per installation through Paessler Router Traffic Grapher (PRTG) Network Monitor, network monitoring can be tailored to your needs. Even a netbook can monitor on average 1,500 sensors, meaning the demand of PRTG on your system is minimal.
The ability to send IT/DevOps push notifications via the preferred communication channel (e.g. email, text messaging, etc.) means that you can ensure the right person knows at the right time when there is a slow or failing sensor, or when sensor channels break predefined threshold values (i.e. when there’s a problem).
Uptime Status Communication Matters
What does all of this have to do with sharing uptime status? StatusCast has been built to integrate with application performance monitoring (APM) solutions like Paessler’s to translate the information your IT/DevOps team receives from tools like PRTG into an update your end users can understand. Just like DevOps can receive push notifications from PRTG when the network is experiencing issues, you can allow your end users to subscribe to alerts via their preferred communication method.
Though they will never appreciate problems with accessing or using your application, end users do appreciate the transparency and convenience of a timely uptime status. By providing this in language they can understand (i.e. non-tech literate) and in a way that does not take time and attention away from IT/DevOps when they need to be focusing on repairing the issue itself, you are ensuring service disruptions have the minimum impact possible on your customers and as a result on your business.
