<h3>I do not want filebeat to report any metrics to elasticsearch.</h3>
<p>Once I start the deamon set I can see the following message:</p>
<pre><code>2020-03-17T09:14:59.524Z        INFO    [monitoring]    log/log.go:118  Starting metrics logging every 30s
</code></pre>
<p><strong>How can you disable that?</strong><br />
Basically what I think I need is <code>logging.metrics.enabled: false</code> or is it <code>monitoring.enabled: false  </code>?
I just cannot make it work. I'm not sure where to put it. The <a href="https://www.elastic.co/guide/en/beats/filebeat/current/configuration-logging.html" rel="nofollow noreferrer">documentation</a> just says to put it into the logging section of my filebeat.yaml. So I added it on the same intendation level as &quot;filebeat.inputs&quot;. To no success... - where do I need to put it? Or is it the completely wrong configuration setting I am looking at?</p>
<blockquote>
<p><a href="https://raw.githubusercontent.com/elastic/beats/master/deploy/kubernetes/filebeat-kubernetes.yaml" rel="nofollow noreferrer">https://raw.githubusercontent.com/elastic/beats/master/deploy/kubernetes/filebeat-kubernetes.yaml</a></p>
</blockquote>
<pre><code>---
apiVersion: v1
kind: ConfigMap
metadata:
  name: filebeat-config
  namespace: kube-system
  labels:
    k8s-app: filebeat
data:
  filebeat.yml: |-
    filebeat.inputs:
    - type: container
      paths:
        - /var/log/containers/*.log
      processors:
        - add_kubernetes_metadata:
            host: ${NODE_NAME}
            matchers:
            - logs_path:
                logs_path: &quot;/var/log/containers/&quot;

    # To enable hints based autodiscover, remove `filebeat.inputs` configuration and uncomment this:
    #filebeat.autodiscover:
    #  providers:
    #    - type: kubernetes
    #      node: ${NODE_NAME}
    #      hints.enabled: true
    #      hints.default_config:
    #        type: container
    #        paths:
    #          - /var/log/containers/*${data.kubernetes.container.id}.log

    processors:
      - add_cloud_metadata:
      - add_host_metadata:

    cloud.id: ${ELASTIC_CLOUD_ID}
    cloud.auth: ${ELASTIC_CLOUD_AUTH}

    output.elasticsearch:
      hosts: ['${ELASTICSEARCH_HOST:elasticsearch}:${ELASTICSEARCH_PORT:9200}']
      username: ${ELASTICSEARCH_USERNAME}
      password: ${ELASTICSEARCH_PASSWORD}

    logging.metrics.enabled: false
---
</code></pre>

lapsus
<p>The <code>filebeat.yml</code> is configuration file that mounted at <code>/etc/filebeat.yml</code> in the <code>filebeat</code> <code>DaemonSet</code>.</p>

<p>There are <a href="https://www.elastic.co/guide/en/beats/filebeat/current/directory-layout.html" rel="nofollow noreferrer">directory layout</a> and <a href="https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-reference-yml.html#filebeat-reference-yml" rel="nofollow noreferrer">configuration reference</a> pages for <code>FileBeat</code> in elastic.co documentation.</p>

<p><strong>Update:</strong></p>

<p>The <code>logging.metrics.enabled: false</code> will only disable internal metrics.
Take a look at this <a href="https://discuss.elastic.co/t/non-zero-metrics-in-the-last-30s-meaning/173970" rel="nofollow noreferrer">post</a>.</p>

<p>Note the difference between this <code>INFO</code> log for the internal metrics:</p>

<pre><code>2019-03-26T16:16:02.557Z INFO [monitoring] log/log.go:144 Non-zero metrics in the last 30s
</code></pre>

<p>And the one in Your case:</p>

<pre><code>2020-03-17T09:14:59.524Z        INFO    [monitoring]    log/log.go:118  Starting metrics logging every 30s
</code></pre>

<p>Unfortunately this configuration will not stop <code>FileBeat</code> from reporting metrics to <code>ElasticSearch</code></p>

<p>Hope it helps.</p>
