Skip to content
This repository has been archived by the owner on Jul 27, 2023. It is now read-only.

Turn down log levels on most chatty services #1241

Merged
merged 14 commits into from
Mar 10, 2016
Merged

Conversation

BrianHicks
Copy link
Contributor

  • Installs cleanly on a fresh build of most recent master branch
  • Upgrades cleanly from the most recent release
  • Updates documentation relevant to the changes
  • Rebases cleanly onto the latest master

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:

  • set Consul, consul-template, MantlUI, Mesos, ZooKeeper, Chronos, and Marathon's log levels to WARN
  • install fail2ban to reduce log spam from sshd and improve cluster security when over IPv4

@BrianHicks BrianHicks changed the title Feature/fewer logs please Turn down log levels on most chatty services Mar 7, 2016
@BrianHicks
Copy link
Contributor Author

Just to drive the point home, here's what this looks like in Kibana:

image

(two days over the weekend I left the cluster running, then fixed Marathon on Monday. That's why the long plateau.)

@@ -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
Copy link
Contributor

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?

Copy link
Contributor Author

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.

@ryane ryane added this to the 1.0.4 milestone Mar 7, 2016
@ryane
Copy link
Contributor

ryane commented Mar 9, 2016

applied cleanly over a 1.0.3 cluster on GCE.

@ryane
Copy link
Contributor

ryane commented Mar 9, 2016

Installed cleanly on a fresh build of most recent master branch (GCE)

were you going to add more docs? otherwise, lgtm

@BrianHicks
Copy link
Contributor Author

Yes, I'll add docs.

@ryane
Copy link
Contributor

ryane commented Mar 9, 2016

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'

@BrianHicks
Copy link
Contributor Author

@ryane I'm not sure what you're asking actually. Are you saying that we should change it or should not change it?

@ryane
Copy link
Contributor

ryane commented Mar 9, 2016

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
Copy link
Contributor Author

@ryane
Copy link
Contributor

ryane commented Mar 9, 2016

@BrianHicks I was referring to the consul service itself:

$ consul monitor
2016/03/09 22:36:37 [INFO] agent: Synced check 'distributive-zookeeper-checks'
2016/03/09 22:37:36 [INFO] agent: Synced check 'distributive-common-checks'
2016/03/09 22:37:59 [INFO] agent.rpc: Accepted client: 127.0.0.1:56836

log_level can be set in /etc/consul/consul.json (https://www.consul.io/docs/agent/options.html#log_level)

ryane added a commit that referenced this pull request Mar 10, 2016
@ryane ryane mentioned this pull request Mar 10, 2016
4 tasks
@ryane
Copy link
Contributor

ryane commented Mar 10, 2016

since this has already been tested as-is, I'm just going to merge it. I opened #1256 with the consul log level.

ryane added a commit that referenced this pull request Mar 10, 2016
Turn down log levels on most chatty services
@ryane ryane merged commit 8ce335a into master Mar 10, 2016
@ryane ryane deleted the feature/fewer-logs-please branch March 10, 2016 13:14
ryane added a commit that referenced this pull request Mar 16, 2016
@ryane ryane modified the milestones: 1.0.4, 1.1 Mar 17, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants