Failures every 30 minutes in 3.2?


I'm using Simon to monitor various ressources on my company's network. When I updated from Simon 3.1.1 to 3.2, my checks started to fail every 30 minutes.

Here are some details : I have about 20 checks running, set to run every minute. The network is rather new and served with a Gigabit switch. The checks use Ping, and are set to send 10 packets. A failure is triggered by an average ping latency greater than 100ms, a lost packet, or when the test takes longer than a minute.

Every 30 minutes, the check fails with a "check time" superior to 1 minute, then immediately recovers (the next check is only one minute away). Average check time is 10 secs.

Running ping in a console shows that average ping times for the services I'm checking are in the 10-20ms range, but I can see a couple of spikes, every couple of times when a single ping packet takes anywhere from 50 to 200ms. The server and the network is lightly loaded.

When I increase the acceptable average ping latency, failures get less frequent. However, since the problem went away when I reinstalled Simon 3.1.1, I think that this is really an issue with the 3.2 release.

Any help would be appreciated.

Best Regards,

403 can be a valid response


I have a test that checks the response of a website to see whether the webserver on that machine is running...any response is a good response. A few days ago, the owner switched that site to be private and Simon now gets the error code 403 as response. 403 is an error msg from a running webserver and therefore is a valid response for this test but Simon insists in sending out alarms telling everybody that the test was unsuccessful. I tried filters and checking of parameters but no success.

Is there a way to teach Simon that the test really was successful despite the error and if yes, how would I do that? I had to turn this test off completely because of all the false alarms we have gotten. The former sent out an alarm on every test and now we lack the info altogether. Neither is satisfactory.

Moving Simon setup to a different Mac

I have a few Simon tests set up on one Mac, but now that I've figured out what I'm doing, I'd rather run Simon on a different machine. Is it sufficient to move everything in ~/Library/Application Support/Dejal/Simon to the other Mac, or are there other files that I might need?


Syndicate content