Overseer 5.0.114 has been released

Posted on February 20th, 2013

I’ve just released a new version of Overseer network monitoring software, 5.0.114. This version fixes a bug that could happen if a default was set under tools->options->defaults, and then that Schedule, Notification Group, Password, or Resource Group was subsequently deleted. Going back into the options screen and clicking save would throw an error.  This version fixes that problem.

This version also fixes a problem a specific customer had with OverseerSvc’s default TCP port assignment. The default has been tcp 12345 for years– even though this is a local port for communication between the Overseer and its own service– and nothing that needs to be passed through firewalls, etc… This customer had another product, “Trend Micro Common Client Communication Service”, that was listening on port 12345, which caused the Overseer service to crash trying to use this port.  I have changed the default port that OverseerSvc uses to 12344, and made this port customizable in the registry. Considering Overseer only uses this to communicate with itself via ‘localhost’, this shouldn’t cause anyone any issues, nor require any firewall changes, etc.


Overseer 5.0.113 has been released

Posted on February 16th, 2013

I just released a new version of Overseer Network Monitoring Software, 5.0.113. This version adds a feature requested by a customer, to be able to edit the dependencies on multiple resources at once. This is done by selecting multiple resources and right click->edit. This puts you in multi-edit mode. Now, any changes to dependencies will apply to all resources that you just selected.

 


MSSQL Log file is too large

Posted on February 14th, 2013

When using MSSQL for Overseer’s database, sometimes the transaction log will grow way too large. This is due to the default setting in MSSQL of ‘Full’ recovery model, instead of ‘Simple’. Overseer should ideally be run with a “Simple” recovery model to keep this log file from getting out of hand. To do this, please follow these steps:

 

  1. Open Microsoft SQL Server Management Studio
  2. Expand ‘Databases’, and find your Overseer database, and right click->Properties
  3. Select  ‘Options’ on the left
  4. On the next screen, select “Simple” for the recovery model, and then click OK

 

Now, if your log file is already very large, you’re going to want to shrink it. You can do this through the SQL Management Studio GUI, as well. To do so, simply follow these steps:

  1. Open Microsoft SQL Server Management Studio
  2. Expand Databases, and find your Overseer database.
  3. Right click on the database, and go to Tasks->Shrink->Files
  4. Choose the ‘Log’ file type, and click OK
  5. Wait for the process to complete, and provided you’ve set the recovery model to ‘Simple’, you shouldn’t have to do this again.

 

 


Overseer 5.0.112 has been released

Posted on February 7th, 2013

I have just released a new version of Overseer Network Monitor. This version adds the ping latency value to the dData field in the CheckLog table. Since users can now use MSSQL as Overseer’s database, more users are requesting that this sort of data is logged, and I’m more than happy to oblige. While Overseer may not use this data(other than display in the history grid), customers may choose to run reports based on this data.


Overseer 5.0.111 has been released

Posted on February 1st, 2013

I have just released a new version of Overseer, 5.0.111. When using Overseer to monitor a SQL Server, a user was experiencing an error, “Machine name may not contain backslashes”. This ended up being a problem when using the DBQuery resource type, monitoring MSSQL using a named instance(i.e. SERVER\instance) and Windows integrated authentication. This bug has now been fixed.


Overseer 5.0.110 has been released

Posted on February 1st, 2013

I’ve just released a new version of Overseer network monitoring software. This has seemingly minor changes, but potentially with major impact to those that it affects. First, Overseer should now run with UAC turned on. If you’re an admin running with UAC turned on(the default on Windows), Overseer will now prompt for administrative privileges when starting. This will avoid an error upon start.

This version also makes a change so that the DBQuery resource type will log scalar data from a check into the CheckLog Overseer database table. This is useful for those with the MSSQL add-in and are looking at the checklog table for some reason(potentially reporting).