Beats: Disable monitoring metrics on filebeat 6.2

[EndlessTundra]

I posted in the forums about this (https://discuss.elastic.co/t/filebeat-6-2-seems-to-be-monitoring-the-server-its-running-on/118865), but I'll repeat here:

After upgrading to filebeat 6.2 I'm seeing this constantly in the logs:

2018-02-07T09:55:12.077-0500    INFO    [monitoring]    log/log.go:124  Non-zero metrics in the last 30s        {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"tic\
ks":70,"time":74},"total":{"ticks":350,"time":360,"value":350},"user":{"ticks":280,"time":286}},"info":{"ephemeral_id":"980b9b03-bf44-494b-8911-be176eb29bd7","uptime":{"\
ms":30014}},"memstats":{"gc_next":6974496,"memory_alloc":5717152,"memory_total":57507792,"rss":20787200}},"filebeat":{"events":{"active":22,"added":1316,"done":1294},"ha\
rvester":{"open_files":4,"running":4,"started":4}},"libbeat":{"config":{"module":{"running":4,"starts":4},"reloads":1},"output":{"events":{"acked":1282,"batches":28,"tot\
al":1282},"read":{"bytes":168},"type":"logstash","write":{"bytes":189400}},"pipeline":{"clients":8,"events":{"active":22,"filtered":12,"published":1304,"retry":60,"total\
":1316},"queue":{"acked":1282}}},"registrar":{"states":{"current":12,"update":1294},"writes":40},"system":{"cpu":{"cores":32},"load":{"1":5.54,"15":4.42,"5":4.71,"norm":\
{"1":0.1731,"15":0.1381,"5":0.1472}}}}}}

I don't understand why filebeat would be doing this since we have metricbeat for that purpose? Can we get a way to turn this off? It is just spamming the logs and sending unneeded information to my logstash servers.

[andrewkroh]

Please don't cross-post issues.

[EndlessTundra]

I'm not sure what you mean by "cross-post". The Elastic team member in the forums told me to post a bug report here.

[andrewkroh]

Sorry. I read the last post on the Discuss topic and it appeared we answered the question (which is to set logging.metrics.enabled: false) and thought this was duplicate.