The History Of WinMonitor
The creators of WinMonitor have a decade of experience with Enterprise Class monitoring products such as CA Unicenter TND,TNG & NSM, and Microsoft Operations Manager (MOM) and System Center Operations Manager (SCOM).
The design, implementation and support of these products is best suited to very large organizations with hundreds of servers as there is a large planning investment, and expenditure required.
While implementing these systems it became clear there was a need for a product that would address the monitoring and alerting requirements of smaller environments which had a smaller number of servers, and a smaller support staff who did not have the time and expertise necessary to work with complicated enterprise monitoring products.
The predecessor versions of WinMonitor were created in 2003 in order to produce a Monitoring and Alerting product that was:
a) Quick and Simple to implement
b) Reliable
c) provided the core base monitoring of Availability, Disk Space, and Service status.
The resulting monitoring product has been used successfully in production environments, most notably in monitoring systems whose role was to alert emergency services of Lahar Detection.
Other production WinMonitor implementations have been particularly useful where the use of other products could not be justified because of the cost and effort required.
This version of WinMonitor has used the same proven base code features, and has introduced new features such as the abstration of all custom configration into a single external .ini file.
Some features present in older versions have even been removed, in a focussed effort to ensure that reliability and ease of use is paramount, which is in marked contrast to other products.