[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "check file" not working as expected

From: Guillaume François
Subject: Re: "check file" not working as expected
Date: Thu, 23 Feb 2017 16:40:53 +0100


If I remember well, file content testing is incremental. 

So when you unmonitor when the last read line is set to, let's say line 123
Then alerting content is written in the file to line 1456 and 1754 during its lifetime while it is unmonitored.

When file is at line 2000, you monitor it again then Monit resume to line 1234 and found occurrence at line 1456 and 1754.

I suppose Monit store the line pointer to its state file and I'm not aware of a way to modify its binary content.

Unfortunately, it seems that the default, and only, Monit behavior is not matching your need. Martin could probably confirm it ?

Best is to ask for an improvement to be able to specify where to resume the file content check:
Again, it is based on my memory. It could have changed or be wrong from the start.

Best Regards.

2017-02-23 15:58 GMT+01:00 <address@hidden>:

we use monit to monitor application logfiles for certain strings like that:

check file appl1-log with path /some/where/appl1-log
if match "whatever" then alert

In case of a database maintenance, we set any of these to "unmonitor", e.g. "monit unmonitor appl1-log", so that we don't get flooded unnecessarily with unwanted mails. That works.

But if we monitor them again after maintenance is finished, then we always get a mail for matches that were found in the meantime. I expected the search to be started at the end of the file when running "monit monitor appl1-log". How can I achieve that?


To unsubscribe:

Version: 3.1
GCS/IT d(+) s++:- a C++$ ULC(+)>+++$ !P--- L+>$ !E---? W+++$ !N* !o-- K--? w(+) !O---? !M- !V--? PS+? !PE Y+ PGP++>+++ !t-- !5 !X- R(+)>++* tv-? b(-) DI !D- G(+)>+ e+++ h--() r->$ y?*

reply via email to

[Prev in Thread] Current Thread [Next in Thread]