Posted on August 20th, 2010
A user recently contacted us with a problem. Every time he created a resource, it would send a notification saying that the resource had been down for longer than it had been. After diagnosing this issue with the customer, I determined that the problem was that Overseer wasn’t cleaning up all historical records for old resources. The user had deleted resources, but their history remained. Due to key re-use in the SQLite database engine, these records were then automatically linked with a new resource, causing problems.
This version of Overseer Network Monitor fixes this problem.
Posted on August 19th, 2010
This build fixes a problem with the notify after time setting.
Posted on August 15th, 2010
This version of Overseer Network Monitoring Software fixes a problem with the skin not saving when changed in the Options window. This bug was fixed after a user contacted us to inform us of this problem. If you’re experiencing a problem with Overseer that you believe might be a bug, please let us know so we can fix it.