-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Textfile Log Error Message Noise - v0.15.0 #704
Comments
Strange, I am not able to reproduce this error with no textfile directory or an empty textfile directory. I will have to look over the code to see if I can trace what's going on. |
The same issue with a package installation:
And if execute:
|
Solved it ? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Host operating system: output of
uname -a
4.4.0-1035-aws #44-Ubuntu SMP Tue Sep 12 17:27:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
node_exporter version: output of
node_exporter --version
version=0.15.0, branch=master, revision=f3a70226025bf81e55eaf9d7386f9f7b3a267694
node_exporter command line flags
Are you running node_exporter in Docker?
Docker version 17.07.0-ce, build 8784753
What did you do that produced an error?
Started the docker container with the --collector.textfile.directory='/etc/node-exporter' directory specified with no files, or a file with a static value
What did you expect to see?
No errors
What did you see instead?
Continuously stacking error messages in docker logs, incrementing until the log messages are enormous and make the logs nearly unreadable on every poll interval. It's seriously noisy, and seems broken to error on an empty directory, especially when it spams every polling interval if you don't specify a directory! If you don't specify a directory, the logs are spammed with this :
If you do specify a directory, even if it's empty, you end up with enormous log spam that looks like this :
The text was updated successfully, but these errors were encountered: