Applications and Infrastructure Monitoring

In the last century, there used to be applications that used to write logs to text files, which stayed right on the server. On one bad day, customer(s) would complain about something not working. A technical team is summoned which tries to find the needle in the haystack by combing through huge log files - that is, if they are able to get hold of them from the live servers. Troubleshooting the problem starts happening after this point. In the meantime, a few hours have already passed and the customer(s) have already developed a crack in the trust in your product's quality.

​

Cut To: The contemporary scene.

The application fails to process a request. Logs capture the errors which are streamed in real-time to the distributed search and analytics engine whose alerting feature sends emails to the technical support team immediately. Dashboards start showing a red flag. Call centres get email alerts about the situation. An automated courtesy email is sent out to the affected customers informing them of the glitch and that the technical team is already working on it, which is truly happening at the back office as soon as the technical support has received the email about the glitch.

Even proactive use cases are possible. E.g. at some point, the monitoring system even sends caution emails to the technical support team such as "Auto-Scaling failed for Target group. Reached CPU utilization threshold". This helps avoid a disaster. As they say - Large fires could be extinguished by pouring a cup of water...at the right time.

​

Does your Application and Infrastructure Monitoring method fit the second scenario? If not, we would be glad to help and bring your customer satisfaction ranking to get the jump it deserves.