-
Notifications
You must be signed in to change notification settings - Fork 617
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
Excessive consul logging #408
Comments
That means your consul state changes every second. Check for flapping services or - more likely - volatile data in the health check output. Like time stamps or process ids or something else that changes every time the check is executed. There are mitigation procedures on the consul side. It in general I advise to try and fix the root cause first. |
@magiconair I also have an excessive number of these in my logs. Every few seconds or so, and sometimes several in rapid succession. None of my services are flapping. I think maybe the consul state changes every time a check is performed. I have many service checks that are performed every 10 seconds. I agree with OP, I think DEBUG level would be more appropriate for these messages. |
This patch changes the log level for Consul raft log changes from INFO to DEBUG so that most users will not see this anymore. High change rate is usually an indicator for flapping services or health checks with volatile output like timestamps but that problem should be dealt with on the Consul side. A PR for #368 will to add an indicator for the change rate of the Consul state. Fixes #408
…ebug Issue #408: log consul state changes as DEBUG
This issue (hashicorp/consul#3642) fixed in 1.0.2 could cause a lot of extra churn for services with tags. |
Thanks @slackpad |
Maybe I have something misconfigured in consul (very possible) but fabio logs a lot of messages like
2017/12/12 20:27:27 [INFO] consul: Manual config changed to #4980182
nearly every second. If that is normalish then I don't think it is very useful at the INFO log level and should be at the DEBUG level as it provides no useful information unless you were heavily into debugging something. Just my opinion.
The text was updated successfully, but these errors were encountered: