Overseer 5.0.162 is now available

Posted on October 24th, 2014

I’ve just released a new version of Overseer. This version adds support for ‘Telus’ as an SMS carrier. It also is the first Overseer installer and executables to be code-signed using our new code signing certificate. This was an expensive certificate to purchase, but I feel it was required due to Google and Microsoft displaying warning messages about Overseer not being ‘commonly downloaded’ to end-users scaring them away from downloading Overseer.

Overseer 5.0.158 is now available

Posted on October 20th, 2014

I’ve just released a new version of Overseer Network Monitor, 5.0.158. This version adds a ‘start service’ and ‘stop service’ options when right clicking a Windows Service resource type. This can be useful to some if you need to force a restart of a Windows Service remotely.


Overseer 5.0.155 is now available

Posted on February 27th, 2014

I’ve just released another version of Overseer. This version includes a few changes requested by a few customers.

The first change is to add a ‘Fail If’ type to the FTP monitoring ability in Overseer. The specific types added(in addition to the obvious FTP server unreachable/unavailable), is to count the # of files in the specified FTP directory(specified in the URL, i.e. ftp://server/directory/). This counts all files(including directories), and will fail if too many or too few files are present. This can be very helpful for monitoring to see if automated file-based processes have stopped processing for some reason.

The other changes are to add new columns. I added a “Up/Down time” to the main resource list, which shows the downtime for any resource that is down, but also shows the up-time for any resource that is online. Note that the up-time is based on Overseer’s knowledge of the resource last being down, so when you first update, the up-time might be under-stated if it hasn’t gone down recently.

In addition to the up/down time column, I added a “Disk Space %” column to the resource list view if the filter is currently on disk space resource types.

Lastly, I changed the resource list grid to save/restore column widths between runs of Overseer– so once you get your column widths set, you don’t have to keep setting them with subsequent starts of Overseer.

Overseer 5.0.143 has been released

Posted on November 15th, 2013

I have just released a new version of Overseer, 5.0.143. This version adds a ‘Resource List’ report, which a customer requested. This report groups resources by group, and shows the name, type, schedule, notification group, last state, and last check. This can also be exported in the print preview to CSV, Excel, PDF, and more.

Also in this build, and also by request of a customer, is event log filtering by keyword. Some applications don’t properly setup event IDs, so the only way to distinguish between events is using a keyword filter. An event filter can now optionally filter by keyword. Keep in mind that this causes the entire text of the event log records to be downloaded to the Overseer computer when they’re checked, so this type of filter can slow things down– it’s best to filter by source, type, and/or event ID on any filters that you use a keyword filter, if possible.

Lastly, I’ve noticed that sometimes when deleting a resource from Overseer that has a significant amount of history(i.e. has existed for a while), the interface went un-responsive as it completed this data operation. To increase the GUI responsiveness of Overseer, I set this history deletion/housekeeping to happen in the background, allowing the user to continue working in the Overseer application.

Overseer 5.0.140 has been released

Posted on October 11th, 2013

I’ve just released a new version of Overseer. This version addresses a bug that I recently became aware of that affected some people trying to monitor event logs– an error regarding “unauthorized operation” was being reported. This is fixed in this version.

Additionally, I added the ability to drag and drop resources from one group to another, making it far easier to quickly organize your resources into resource groups.

Lastly, I added a simple version check upon Overseer start. Now, when you start the Overseer application, Overseer will check the website to determine the latest version of Overseer, and prompt to update if there’s a new version available.

Overseer Network Monitor 5.0.133 has been released

Posted on August 30th, 2013

I just released a new version of Overseer, 5.0.133. This version focuses on enhancing Website Monitoring. Overseer has been able to check HTTP and HTTPS websites to ensure they’re running for many years. This version adds support for checking the response time, which can be a key sign of site health. Additionally, Overseer can now check to make sure the webpage contains or does not contain specific text. This can also be a key sign that the website is delivering the correct content, and there’s no error being displayed.  Lastly, I added support for SSL expiration checking. One of the most common problem with SSL websites, is no one monitors the certificate expiration– so with this check, you can setup Overseer to warn you within a specific # of days of an expiring SSL certificate, giving you plenty of time to renew it and not have website visitors seeing “certificate expired” error messages.

Overseer Network Monitor 5.0.132 has been released

Posted on August 15th, 2013

I’ve just released another version of Overseer Network Monitor. This is a feature release, containing multiple new features.

First, I’ve added support for monitoring FTP Servers, using the new FTP resource type. If you need FTP monitoring software, this is the perfect feature for you.

Second, I’ve added support for monitoring TCP sockets, using the new TCP Socket resource type. While Overseer can monitor many different protocols, there are still some protocols that Overseer is not natively aware of. This resource type gives you the flexibility to monitor any protocol that listens on a TCP port, and ideally provides a prologue of some sorts. This new resource type checks to make sure a specific host answers on a specific port, and optionally responds with text that contains specified text(i.e. ‘openssh’ for an SSH port). You can also customize how long to wait for this text to show up on the socket after connection.  This is a great way to monitor ssh servers, SMTP server, POP3 servers, and more.

In addition to the 2 new resource types above, I’ve made numerous usability changes to the base Overseer interface. I’ve added an ‘All Groups’ pseudo-group to the left tree, a search box below the resource list, the ability for the resource group tree to use smaller icons, and Overseer now hides resource types in the left tree by default, only showing them if you actually have resources of that type, in that group– this saves a lot of screen real estate, letting you see the meaningful parts of your configuration more easily, with less noise.


Overseer 5.0.126 has been released

Posted on June 17th, 2013

I have just released a new version of Overseer, 5.0.126. This version fixes an error message that would sometimes appear on 5.0.124(released Friday) in regards to index creation.  In addition to this bug fix, I enhanced an undocumented feature, called ‘aggressive event log source detection’. This feature, turned on with the “AggressiveEventLogSourceDetection” setting in the registry, instructs Overseer to look back in the event log to find any event log sources that aren’t properly registered in the system registry. The enhancement I made, was for it to work with the new event log mechanism added in Windows 2008.

Overseer 5.0.124 has been released

Posted on June 14th, 2013

I just released a new version of Overseer, 5.0.124. This version adds some indexes to the Overseer database to improve performance throughout the program– particularly useful with large databases.

Overseer Network Monitor 5.0.119 has been released

Posted on March 23rd, 2013

I have just released a new version of Overseer Network Monitor. This adds support for Sensatronics E4 and E16 devices. Overseer already has supported the EM1 device, but many people have requested support for the E4/E16 devices as well– probably because these devices are less expensive than the EM1 unit, and if you only need to monitor temperature(which is the most common request), the E4 or E16 is the ideal solution.. Anyways, this release adds full support, and re-names the “EM1” resource type to generically the “Sensatronics” resource type, with a drop-down to indicate which model.

Additionally in this release, I’ve added support for the cell phone carrier, ‘ICE’, in Costa Rica. This was asked for specifically by a customer there, and we’re happy to add it.