Filebeat and Docker EE

Hi There,
We have just installed a Docker EE cluster on 10 nodes (3 UCP , 3 DTR and 6 workers) .
Filebeat and Metricbeat are installed on each nodes with this configuration :

  path: ${path.config}/modules.d/*.yml
  reload.enabled: false
  index.number_of_shards: 3
    - type: docker
        - condition:
            - type: docker
                - "${}"
               - add_docker_metadata: ~

As you seen docker logs are caught by Filebeat , parsed and send to Elasticsearch.
Everything works fine but now we would like to activate Kubernetes as Orchestrator (embedded in Docker EE).

Do you ever experienced this configuration with Filebeat ? What is the conf to address Kubernetes api for the autodiscovering ?

Thank you for your help.

Have you considered the kubernetes autodiscovery provider?

Yes, but Filebeat or Metricbeats need to have some informations about kubernetes (like the hostname and the port). I don't find in the documentation a way to declare them inside my Beats configuration.
does it need the kubelet in workers or just the Kubernetes API in Masters nodes ?

Filebeat/Metricbeat auto discovery does connects to the local kubelet and listens to the local event stream.

Also see:

Fyi , Filebeat does not run in a container , it has been installed by a linux package.
It's like a unix agent.
Where can I specify the host and the port of k8s in Filebeat to enable the autodiscover ?

See kubernetes provider docs. The kubernetes providers has the settings in_cluster, host, and kube_config.

Normally host is not configured. Beat tries to discover/select the kubernetes host by these rules:

  • If host is provided in the config use it directly.
  • If the Beat is deployed in the k8s cluster, it uses the hostname of the pod. It uses the pod name to query the pod meta in order to read the node name.
  • If the Beat is deployed outside the k8s cluster, it use the machine-id to match against k8s nodes for the current node name.

That is, if Filebeat is installed on the same host as as the kubelet, it should still be able to find the correct node. If not you can use the host configuration:

  - type: kubernetes
    host: "<node endpoint>"
      - ...
1 Like

Thank you for the example.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.