the fix is part of Monit 5.4, which was released today.
On Mar 16, 2012, at 5:52 PM, Ryan Revels wrote:
Any idea when the next release might be out?
On Thu, Mar 15, 2012 at 11:18 AM, Martin Pala <address@hidden>
Yes, the fix will include sending all pattern matches in one email (not one email per match as it is now)
On Mar 14, 2012, at 3:32 PM, Nick Upson wrote:
In the same area, I would like to be able to have all (matching) changes in one email,
at the moment I monitor a logfile that rarely gets anything written but when it does it writes 4 lines of output which I get at one line per email at the moment as I not been able to find a way to have them all in one email
On 13 March 2012 19:03, Martin Pala <address@hidden>
the content match test is individually applied to every new line which was added since last test. In the case that the line matches, the event is generated immediately => in the case that there are lets say 1000 matching lines, you will receive 1000 alerts. We will fix this - the content match test will send one alert per test per cycle.
On Mar 13, 2012, at 5:38 PM, Ryan Revels wrote:
> I'm using Monit to watch file contents to watch for out-of-memory conditions. The problem is that when this condition happens, I get 1000s of emails within a few seconds because the log starts filling up with repetitive messages.
> I've been unable to get rsyslog or monit (m/monit) to silence the repeats. Any suggestions on how I might do that?
> To unsubscribe: