The document discusses monitoring, logging and tracing tools for Kubernetes including Heapster, Grafana, Fluentd, Elastic Stack, Jolokia and OpenTracing. It provides examples of deploying Heapster with InfluxDB and Grafana for metrics collection, Fluentd to ingest container logs into Elasticsearch, and using Jolokia and OpenTracing for remote access to JMX metrics and distributed tracing functionality.
1. #Perform2017
with Heapster, Grafana, Fluentd, Elastic Stack, Jolokia and OpenTracing
Martin Etmajer @metmajer
Dynatrace, Technology Lead
Monitoring, Logging and Tracing on Kubernetes
55. Why distributed (end-to-end) tracing?
Source: https://research.google.com/pubs/pub36356.html
initiator
services
remote calls
What does the architecture look like?What does the architecture look like?
56. Why distributed (end-to-end) tracing?
Source: https://research.google.com/pubs/pub36356.html
initiator
services
remote calls
Where is most of the time spent?
57. Why distributed (end-to-end) tracing?
Source: https://research.google.com/pubs/pub36356.html
initiator
services
remote calls
How are services invoked?
get an overview of the applications running on the Kubernetes cluster
create, modify and delete Kubernetes resources
troubleshooting (logs)
https://kubernetes.io/docs/user-guide/ui/