Overseer 4.0.10820.00 Released

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.