Monitoring Kubernetes with
Elastic

#whoami
●Wouter De Kimpe
●System Engineer @ Kangaroot
●linkedin.com/in/dekimpew

Introducing: Rancher
●Kubernetes the easy way
●Creating and managing multiple clusters
●Both on-prem and cloud clusters

Challenges of monitoring containers
●Containers come and go: cattle Vs. pets
●Dynamic environment
●Many different endpoints to monitor

Introducing: Elastic Stack
●A stack … For search!
●Not only for aggregating logs or searching data
●Consists of:
– Beats: Lightweight shippers
– Logstash: Transforming data
– Elasticsearch: Scale out database
– Kibana: WebUI for visualizations

The elastic members

The Infrastrucure view
●New addition to Kibana
●Tailored towards monitoring infrastructure
●Logs and metrics within reach in one view
●Dynamic add/remove of k8s workloads

Integrating Elastic in Rancher
●Filebeat and Metricbeat on the k8s clusters
– Can be deployed with helm or the elastic yml
– Deployed as a daemonset on all nodes
●Elasticsearch and Kibana outside the cluster

Yaml to the beat
●Some minor changes and considerations are required to get
metrics and logs in Elasticsearch.
●By default deployed to kube-system
●Metricbeat requires kube-state-metrics to be installed
●Logs to filebeat-%{date} and metricbeat-%{date} by default

Resources
●https://github.com/santascsi/elasticrancher
●https://www.elastic.co/guide/en/infrastructure/guide/current/infrastr
ucture-ui-overview.html
●https://www.elastic.co/guide/en/beats/metricbeat/current/running-
on-kubernetes.html

Demo time!

Thank you!