-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unclear tailing extrapolation? #13
Comments
This is probably coming from the watcher, which uses fsnotify to know when |
This seems like a bug, but certainly related to how the filesystem watcher I suspect it is noticing updates to that file and the message merely states If so, a simple fix is to downgrade the message to a lower severity. On Fri, 6 Nov 2015, 00:13 Ben Kochie [email protected] wrote:
|
handleLogUpdate in mtail/tailer/tail.go:123 is called on all UpdateEvents On 6 November 2015 at 09:24, Jamie Wilkinson [email protected] wrote:
|
👍 😎 |
Thanks! |
We can avoid some strange info log messages and additional checks in the handler methods by doing this. Issue: #13
Hi,
I want to tail
/var/log/exim4/mainlog
so I run mtail using runit like this:That seems to work fine, except that my log is spammed with the following message multiple times per second:
At no point did I tell mtail to care about the reject log nor do I want to tail it since it would taint the metrics. What is going wrong here?
Why does mtail think it should tail an unrelated file that happens to be in the same directory and what can I do about it? It is generating quite a bit of log data…
The text was updated successfully, but these errors were encountered: