ServiceMon Release

Rating: No reviews yet
Downloads: 1692
Released: Oct 19, 2012
Updated: Oct 19, 2012 by wheelies
Dev status: Stable Help Icon

Recommended Download

Application ServiceMon-
application, 1232K, uploaded Oct 19, 2012 - 1180 downloads

Other Available Downloads

application, 252K, uploaded Oct 19, 2012 - 512 downloads

Release Notes

ServiceMon Release 1.1 - What's New

Added support for nested script modules

Previous versions of ServiceMon have only supported one running process. In v1.1 you can add logical groupings within your script to create any number of independent, nested monitor processes within one window.

You can create a Big Visible Chart or Information Radiator for your development team in a few minutes, with a few lines:

  #name "Panel 1"
  http-get "" must-contain "I'm Feeling Lucky"
    #name "Panel 2"
    windows-service-status "spooler", "localhost" must-equal "Running"
    #name "Panel 3"
    ping "" must-equal "Success"

This splits the screen like this:

Double-click on a panel will zoom so it fills the screen. Double-click again to display normally.

Custom colours and thresholds

The standard behaviour is for the screen to change from light green to yellow after one failure, to orange after 2 failures, to light coral after 10, and finally, to crimson as the failure count reaches 100. You can modify the colours and thresholds by adding this line to the top of your script:
#colours "0 failures blue, 1-10 failures purple, 11+ failures red"

You can use any number of threshold ranges, and any named web colour. See the #colours directive for more information.

Added support for monitoring CruiseControl builds

ccnet-build "http://mybuildserver/ccnet/", "MyProject" must-equal "Success"

Added a full screen view

Press F11 to maximise the screen and remove the window's frame. This allows ServiceMon to act as a true Information Radiator

A script can now be passed to ServiceMon on the command line

servicemon "C:\MyScript.mscr"

Added #max-error-age directive

This is used to specify the time after which errors become insignificant. This is useful when monitoring a service or system for failures within a given period.

#max-error-age is particularly effective when combined with the #colours and #email-on-threshold-change directives.

For example, to setup an email notification when a system's availability falls below 99.9% for any 24 hour period:

#max-error-age "24 hours"
#colours "0%-99.9% success-rate red, 99.9%+ success-rate green"
#email-on-threshold-change ""

http-get "" must-contain "Google"

Reviews for this release

No reviews yet for this release.