Well, it’s been a while since the last stable release of PolyMon (June 19, 2007 to be precise).
During that time I have mainly been working on adding post monitoring actions. Essentially this will allow any monitor to execute custom scripts after a monitor has run. Since the status and counter objects are available to these scripts you would in practice be able to perform various actions based on the results of the monitor (for example, if a service monitor fails because the service its monitoring is not running you could start the service up, or if a log file has grown past a certain point you could write a script to purge all or part of the log file, etc).
The action scripting will, for now, support VBScript as well as PowerShell scripts. Technically PowerShell would have been sufficient for any scripting task, but because I’m not sure how many people have taken to PowerShell yet (which I highly recommend, btw), I opted to include VBScript.
I did look into incorporating VB.NET and C#.NET “scripting”, but one of the obstacles I found with this approach was adding references to other .NET libraries at run-time. I could have worked around this problem by providing an Add Reference capability, but it would create other problems such as making sure the referenced libraries are available (and in which location?) on the server that runs the monitors, not just the machine running the management console. Looks like PowerShell is a better approach. Problem there is that Microsoft does not allow redistribution of the PowerShell binaries, so the PolyMon install now requires an additional pre-requisite on top of the usual .NET framework.
The next release of PolyMon which will incorporate this new feature is due in the next couple of weeks. I have yet to fully test it in a working production environment and have to finalize the installer and help files. For the last stable release I took the plunge and switched to Wix for creating the insllation package. The learning curve was relatively steep and I ended up spending far more time that I would have liked – but in the end the effort was well worth it. I highly recommend using WiX if you are creating anything other than relatively basic installers in Visual Studio.
In addition to this new feature several bug fixes will be rolled in (in particular one that addresses the internationalization problems when creating the PolyMon SQL database – thanks to Steinlaus for figuring this particularly frustrating problem out).