-
Notifications
You must be signed in to change notification settings - Fork 414
Turn down log levels on most chatty services #1241
Conversation
@@ -11,6 +11,8 @@ chronos_zk_connect: "zk://{{chronos_zk_auth}}{{ chronos_zk_dns }}:{{ chronos_zk_ | |||
|
|||
chronos_zk_mesos_master: "zk://{{ chronos_zk_dns }}:{{ chronos_zk_port }}/mesos" | |||
|
|||
chronos_log_threshold: WARNING |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add the possible options to the README?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, the options will all be documented once it looks good otherwise.
applied cleanly over a 1.0.3 cluster on GCE. |
Installed cleanly on a fresh build of most recent master branch (GCE) were you going to add more docs? otherwise, lgtm |
Yes, I'll add docs. |
actually, do we want to change the log level for consul itself (in /etc/consul/consul.json)? afaict, this is not set and the default level is 'info' |
@ryane I'm not sure what you're asking actually. Are you saying that we should change it or should not change it? |
The log level for consul appears to still be 'info'. I just wasn't sure if that was intentional or not. Otherwise, we should set it to 'warn', right? |
@BrianHicks I was referring to the consul service itself:
|
since this has already been tested as-is, I'm just going to merge it. I opened #1256 with the consul log level. |
Turn down log levels on most chatty services
This PR turns down the log levels of quite a few components. It takes the total logs per hour down from 45,000-55,000 lines per hour to around 6,000 per hour on a cluster with minimal use.
Changes made: