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.131 has been released

Posted on August 9th, 2013

I’ve just released another version of Overseer Network Monitor, 5.0.131. This fixes a couple bugs. First, was monitoring the local event log when Overseer is running on Windows 8. There was an error when testing the event log resource, “Attempted to perform an unauthorized operation.”  This has been fixed.

Additionally, a user reported a memory leak when Overseer has been running a long time. I eventually narrowed this down to event log monitoring using newer Windows OS’s(Vista/W2K8+)– on both the Overseer end, and the monitored computer end.  I was able to determine the problem and resolve this bug. If you’re experiencing it, please be sure to update to 5.0.131 or higher.


Overseer 5.0.130 has been released

Posted on August 5th, 2013

I have just released a new version of Overseer, 5.0.130. This version changes the maximum’ free disk space’ value(when specified in megabytes) from 999,999MB to 999,999,999MB. This was requested by a customer who has very large backup drives and needs to make sure they have adequate backup space available– so they’re monitoring the free disk space with Overseer.


Overseer Network Monitor 5.0.129 has been released

Posted on August 2nd, 2013

I have just released a new version of Overseer Network Monitor, 5.0.129. This version adds a quick fix for a bug when editing event log filters. Also in this release, is a new feature called Event Log Filter Sets. This lets an administrator define a set of Windows Event Log filters and assign them to multiple event log resources, versus setting up filters on each resource. This is an incredible time saver, making filtering events when monitoring event logs far easier to manage.