Blog Archive

Apr 13 (1)

Mar 13 (4)

Feb 13 (3)

Dec 12 (2)

Nov 12 (7)

Oct 12 (4)

Sep 12 (5)

Aug 12 (6)

Jul 12 (4)

Jun 12 (3)

May 12 (5)

Apr 12 (6)

Mar 12 (8)

Feb 12 (8)

Jan 12 (10)

Dec 11 (8)

Nov 11 (6)

Oct 11 (12)

Sep 11 (10)

Aug 11 (15)

Jul 11 (9)

Jun 11 (12)

May 11 (23)

Apr 11 (10)

Mar 11 (13)

Feb 11 (10)

Jan 11 (5)

Dec 10 (21)

Nov 10 (10)

Oct 10 (10)

Sep 10 (8)

Aug 10 (8)

Jul 10 (10)

Jun 10 (8)

May 10 (14)

Apr 10 (20)

Mar 10 (10)

Feb 10 (3)

Our Blog

Blog RSS

Paul Saunders, 16th July 2012

Application Status

0 comments

When websites or mission critical services go down they can sometimes make headline news. O2 were taken off the Conduce Christmas card list last week when their nationwide mobile phone outage affected almost our entire team. At Conduce Software we have a number of measures in place to ensure our web applications are as resilient and robust as possible, but it never possible to be assured of 100% reliability. We've been using the PRTG Network Monitor tool to help us keep an eye on our various web and server assets for a while. This does a great job of keeping us alerted, but it's quite a complex and technical tool that we wouldn't necessarily want to present to our customers.

The main driver to improve visibility of application status has been our new etechlog application. This is a mission critical system for our customers with users potentially anywhere in the world accessing the system 24/7. To help assure users of application status in the event of a problem I designed a "Server Status" screen which we wanted to include in the management application dashboard.



This morning Mark completed the first phase of development of the monitoring application. Here's a live view of the actual etechlog application status page.
We use the PRTG Network Monitor API which delivers the status of each device sensor that we have in place. Mark has developed a quick and simple web application that allows us to add some additional meta-data about those various sensors and deliver those to a simple web page which refreshes every 60 seconds. I wanted the status page to be as simple as possible where it was obvious if there was a problem and where a description is given as to what the consequences would be for a specific issue. The idea is that we can drop that status content into an iframe on to any web page as I have done here. For the etechlog we are in the process of adding this page to the dashboard of the management application. We've set up sensors for all of our other customer's hosted applications and have created an Application Status page on our website so that they can view the status of their system at any time.

The next phase will see us show a status history and include additional status values such as server response times and database query results. Let me know what you think.

Related Posts:
Lists v2.0
Etechlog Sneak Peek
The New AircraftIT Columnist

Author: Paul Saunders

This article has 0 comments

Bookmark this...

Linked In Twitter Digg Delicious StumbleUpon Reddit Facebook Propeller

© Copyright Conduce Group 2013

Accessibility Statement | Site Map | Privacy Policy

XHTML | CSS