Overseer 4.0.1029.01 Released

Posted on October 29th, 2009

I’ve just released a new version of Overseer Network Monitor that changes how Overseer 3.0 imports work. Previously to this version, Overseer would import all your resources and immediately activate them. Overseer 4.0 does not import Overseer 3.0 passwords for security reasons, however– you must specify these passwords after the import.

One user suggested making the imported 3.0 schedules inactive, so they could set passwords and then activate them– rather than have all their resources immediately fail their checks due to missing passwords.

This version does just that. Now Overseer 3.0 imports will create schedules that are marked as ‘inactive’ initially.


Overseer 4.0.1027.01 Released

Posted on October 27th, 2009

I’ve just released a new version of Overseer that fixes a problem with notifications for some SMS carriers.


Overseer 4.0.1026.03 Released

Posted on October 26th, 2009

This new version of Overseer Network Monitoring Software includes a great new feature that’s been requested by many customers.

Overseer 4.0.1026.03+ now supports ‘schedule exceptions‘. This allows users to specify maintenance periods. Please be sure to see the blog post on how to setup schedule exceptions.


Schedule Exceptions

Posted on October 26th, 2009

Many customers have asked for the ability to specify maintenance periods for their system and network monitoring with Overseer. Well, as of Overseer 4.0.1026.03, this feature is now supported in Overseer! In this blog post, I’ll go over usage of this new feature.

Go to Manage->Schedules:

Next, select your schedule:

Once you’ve selected your schedule, you’ll be presented with the standard Overseer schedule screen:

Click the ‘Exceptions’ button and you’ll be presented with the main Schedule Exceptions screen:

Right click on the calendar and select ‘New Exception’ or ‘New Recurring Exception’ if your maintenance period is regular(i.e. every Tuesday and Sunday night):

Now select the time periods/days for your maintenance period, and click ‘ok’ on each screen to get out. That’s it.

Schedule exceptions will prevent your resources that use this schedule from being monitored during these maintenance periods.


Overseer 4.0.1023.01 Released

Posted on October 23rd, 2009

I’ve just released a new version of Overseer Network Monitor that fixes a problem that prevented the ‘count’ field for ping resources used for network device monitoring from saving properly.


Overseer 4.0.1022.01 Released

Posted on October 22nd, 2009

I’ve just released a new version of Overseer that fixes a problem with EM1 environmental monitoring units from Sensatronics. The error experienced by users was “Unable to load EM1 config: There is an unclosed literal string”. This was due to a non-standard network/http implementation used by Sensatronics in the EM1 units. Fortunately, I was able to derive a fix so that customers can use EM1 units to monitor the temperature of their servers.


Overseer 4.0.1020.06 Released

Posted on October 20th, 2009

I’ve just released a new version of Overseer that includes a help file.


Overseer 4.0.1020.01 Released

Posted on October 20th, 2009

I’ve just released a new version of Overseer Network Monitor that includes a fix that a customer had with Website Monitoring resources. The problem only affected those using Windows/NTLM authentication for HTTP authentication.


Overseer 4.0.1015.01 Released

Posted on October 15th, 2009

I’ve just released a new version of Overseer Network Monitor that fixes a problem that some 3.0 customers were having when importing Windows Service Monitoring resources. The “restart service” flag was not being imported properly. This has been fixed.


Overseer 4.0.1009.04 Released

Posted on October 10th, 2009

I’ve just released a new version of Overseer Network Monitor that fixes an error when Overseer is run with UAC on with a non-admin account. Generally, Overseer should always be run as an Administrator, and it’s best to have UAC turned off.