back to the monitor

Ringsys WebMonitor 1.1
Reliable web server monitoring.


Reference Manual for version 1.1

The latest information about Ringsys WebMonitor can be found at http://www.websitewatchers.co.uk/
If you have any suggestions concerning additions or corrections to this manual, please send them to: webmonitor1@websitewatchers.co.uk

Read also: Installation Instructions Licence agreement

CONTENTS

1. What is Ringsys WebMonitor 1.1
2. History of Ringsys WebMonitor
3. The main features of Ringsys WebMonitor
4. Useful web monitoring and web testing links
5. What are the web failures, or rather potential risks/problems
6. Monitoring Template
7. Analyzing the logs
8. Your Feedback

1. What is Ringsys WebMonitor 1.1

Ringsys WebMonitor 1.1 is a web monitoring software, which has been designed for reliability, portability and scalability.

The software can be configured easily to monitor one web site, but you have also access to powerful features that will offer you a complete solution for your intranet and internet websites. A cross-monitoring feature is also available that will ensure that your monitors are running properly. For examples of configurations for the Ringsys WebMonitor and successful monitoring patterns, see section '6.Monitoring Template'.

Ringsys WebMonitor 1.1 is fully portable on any standard Unix operating system, and on Microsoft Windows.

2. History of Ringsys WebMonitor

Ringsys WebMonitor was first used as an Intranet web monitor in a banking environment, ensuring that traders and credit managers could access their online data, at any time.

It was then used as a large scale web monitor, checking the availability and the security of thousands of web sites on the Internet, for the benefit of all Internet users.

3. The main features of Ringsys WebMonitor

4.Useful web monitoring and web testing links

WatchMyWebFREE! - free external web monitor
http://www.watchmyweb.com/watchmyweb/

WebSiteWatchersLtd - reliable external monitoring services
http://www.websitewatchers.co.uk/

5. What are the web failures, or rather potential risks/problems ?

Web failures are or can be
- the physical computer hosting the web site going down
- the physical/virtual network connecting the web site to the world going down
- the software delivering the web content being down,
- the firewall preventing legitimate access to the web site
- any of the server-side sofware in fault or hanging
but also,
- server misconfiguration
- proxy, firewall misconfiguration
- files user permissions
- web server user permissions
- broken links
- unauthorized changes made to the content
- external/internal re-routing to a hacked server
- hi-jacking and piracy

6.Monitoring Template

For instance, let's assume we have 2 machines called Computer1 and Computer2. We want a monitoring agent running Live (sending alarms) on Computer1, and a monitoring agent running Cont (contingency) on Computer 2.

Step1: Install webmonitor1.1 on computer 1 & 2.(see installation guide: README.txt)

Step2: on Computer1, open your browser on 'Show Management' at http://computer1:7070/monitor/management.
Add a new agent in 'Policies' Menu (cont ; Computer2 DNS ; port 1099). From now on, the other agent will be monitored.
Add a new URL in 'Policies' Menu (http://computer2:7070/monitor/management ; your email and details ).
From now on you can directly log on the other computer management page and control it. Always look at the url mentionned on your browser window so that you know exactely where you are. Access to computer2 agent management can thus be achieved from a click on the appropriate link within 'console' or 'External Monitoring' menus.

Step3: on Computer2 management page. After installation, the computer2 agent will automatically be set up as a live agent. As a consequence, reset it to 'cont' in 'Policies'. Also, add a new agent (live; computer1 DNS ; port 1099).
Add a new URL in 'Policies' Menu (http://computer1:7070/monitor/management ; your email and details).

Step4 : on both computers, add in 'Policies' Menu all URLS you want to monitor. They will be automatically added on the 'Console' Menu.

Step5: your monitoring is properly set up on your system and checking your critical applications.

Step6: configure your escalation scheme.(1st, 2nd and 3rd line alarms) in 'Policies'.
Also mention the 'sender e-mail' in 'Properties/Ouraddress' (all alarms sent by email will be entitled to that address. example : monitoring@yourcompany.co.uk)

Step7:Now, it is possible to change all intrinsic monitoring properties. While changing properties, turn OFF/ON autorefresh function at the bottom 'Console' menu, so that you won't be bothered by screen refreshment periodically erasing data you try to put in.
In order to change monitoring properties, go to 'Properties' Menu and click on 'help' buttons before committing changes.
All properties and allowed values are documented in all 'Help' menus.

The default properties initialy run by your Webmonitor1.1 software are found in Initial Webmonitor Properties.

7. Analyzing the logs

The application produces three logs: All the logs are in CSV format, so they can be post-processed for example with MS Excel.

The information in monitor.log is appended to monitor.log.append (if you use the plaintext database) or to the table event (if you use a relational database like Oracle or Sybase).
 

8. Your Feedback

Send any feedback, bug report or suggestion to: webmonitor1@websitewatchers.co.uk
You can report bugs and issues through our 'Help & Feedback' section while browsing Webmonitor1.1 management web page.
Report bugs and issues
(use a valid email address)