Too many syslog errors on failed ping test

Issue #588 resolved
cgzones
created an issue

When a ping test fails, an error is produced for each missing response. When using syslog logging, this results in:

Apr 05 15:07:58 debianserver monit[362]: Ping response for debian.org 1/5 timed out -- no response within 10 s
Apr 05 15:07:58 debianserver monit[362]: Ping response for debian.org 2/5 timed out -- no response within 10 s
Apr 05 15:07:58 debianserver monit[362]: Ping response for debian.org 3/5 timed out -- no response within 10 s
Apr 05 15:07:58 debianserver monit[362]: Ping response for debian.org 4/5 timed out -- no response within 10 s
Apr 05 15:07:58 debianserver monit[362]: Ping response for debian.org 5/5 timed out -- no response within 10 s
Apr 05 15:07:58 debianserver monit[362]: 'debian.org' ping test failed

All of the entrys have the priority "err" (3)

From my point of view the option check host debian.org with address debian.org if failed icmp type echo **count 5** with timeout 10 seconds for 2 cycles then alert is exactly for this case, when single pings are acceptable to fail.

Please lower the log priority of the Ping response for debian.org a/b timed out message to "notice" (5)

Comments (4)

  1. cgzones reporter

    Thanks for the quick fix.

    A similar behavior concerns the general resource matching: When using a configuration if cpu usage (wait) > 15% for 10 cycles then alert monit logs on a lonely violation Apr 11 01:24:30 server02 monit[2315]: 'localhost' cpu usage of 12.3% matches resource limit [cpu usage>10.0%]["err" (3)], with correctly generating no alert.

  2. Log in to comment