The document describes a web service monitoring application that was developed to address the challenges of constantly monitoring websites and services. The application uses a Windows service that checks URLs stored in a database at configured intervals, makes requests to the URLs, stores the results in another database, and notifies contacts if any URLs fail. A web page displays the real-time status of the monitored systems and can generate reports on historical data. The application was built using ASP.NET, C#, SQL Server, and unit testing frameworks.

1. What we have developed…
The main aim is to show the challenges we were given and the
solutions we presented.

2. Web service monitor
 Problem : The web applications that run in live should have a constant
monitoring 24X7 with out which is to accept the risk of your web site
going down and you will get to know only when end user informs the call
center.
 After which call center guys engage technical support team to restore
the service. All this process takes much time and would result in the
service unavailability and eventually financial loss.
 The challenge of maintaining a web application is that it requires a
constant monitoring , suppose if you have ‘n’ number of small web sites
and manual monitoring is not economical and almost impractical.
 The application given in the next slide shows how to do it in a machine
way.

3. Web service monitor
 This application can monitor any kind of web application (built on any
technology ) or service (Any service to which the application can connect
to).
Technologies used :
1) ASP.NET 4.0 Framework, c#.
2) MS SQL 2008.
3) Unit testing is using Microsoft Unity frame work.
4) Static code analysis using coverity static code analysis tool.

4. A brief design of the application is given below.
MS Sql DB (DB1)
• Holds the
Records services and
table web sites to be
monitored.
Windows
service
(WS1)
Web page which shows
the services being
• Holds the results monitored (WA1)
Results of the websites
table and services
being monitored
MS Sql DB (DB2)

5. How the application works
 The windows service WS1 in the diagram picks up each URL one by one
from DB1 and fires a http web request to the URL in the same as our
normal web browser does and stores the results in the DB2.
 When the URL is fired from the WS1 if the URL is not reachable a mail
notification will be triggered to the interested parties so that appropriate
action can be taken.
 WS1 will complete one cycle of accessing all the entries in DB1 and then
sleeps for the specified amount of time specified in the WS1
configuration file. With this we can control the monitoring intervals.
 Each entry has in DB1 has a contact list of the interested parties whom
should be notified upon the failure of the particular service or website.

6. How the application works
 WS1 makes an entry in DB2 each time when it tries to verify the
request.
 DB2 has all the details of the requests fired from WS1 the request time
response time and the time taken to serve the request.
 WA1 is the graphical user interface which shows the real time health of
the systems that are being monitored.
 If any of the service of application fails that particular entry is shown as
red so that the standby team can take an appropriate action.
 The WA1 can generate a report with the data of previous day to know
the health of the system for the entire day.