Looks like content match buffer is not more than 6 lines in our case,
while some more entries was in the log when monit was executed.
Is there a configuration option that limit this buffer ?
Le 21/02/2018 à 12:53, Eric Pailleau a écrit :
this is a problem actually for us.
We tried to do a workaround by treating several lines given as
argument to our scripts,
but looks like monit miss some lines when already executing a command
on a match.
Some new lines added in same time slot as not treated, even if we
the script for an immediate return.
Or there is maybe a limit on number on lines treated at once ?
Any idea to solve our issue ?
Le 19/02/2018 à 23:37, mart...@tildeslash.com a écrit :
yes, see Monit 5.4 changelog:
* The content match test now sends one event per cycle and pattern.
Even if there are multiple lines matching the same pattern, only
one event will be generated. Also the event rate is fixed now, so
it is possible to require match for X cycles before generating the
On 19 Feb 2018, at 16:47, Eric Pailleau<e.paill...@numlog.fr> wrote:
we see a difference in monit regular expression check of a file.
On former monit version looks like monit did a command on each line found,
while using version 5.9 we got a command with all the lines matching since
file increased its size.
Is there a way to have former behaviour ?