Log structure and tagging
- Name space
- Kubernetes supports multiple virtual clusters backed by the same physical cluster. These virtual clusters are called namespaces
- Pod name
- The group of containers for your application
- Every object created over the whole lifetime of a Kubernetes cluster has a distinct UID
- Image name
- The name of the container image
- Container name
- The container name
- Metrics aggregated over all nodes displayed in SPM overview
- Host / node level
- Metrics aggregated per node
- Pod level
- Metrics aggregated by pod name
- Docker Container level
- Metrics aggregated for a single container
Having these data extracted and structured makes it easy to slice and dice Kubernetes metrics and logs, build log analytics reports, and quickly narrow down to problematic pods while troubleshooting.
Alert rules can be created on both logs and Kubernetes / Docker metrics. All Kubernetes cluster nodes and containers are auto-discovered regardless of where you are running Kubernetes – Google Container Engine, Amazon ECS, Rancher, CoreOS, etc. are all supported.
- Sign up
- Create Logsene App for logs and SPM App for metrics
- Grab sematext-agent.yml and enter your SPM and Logsene App tokens
- Run Sematext Agent as Kubernetes DaemonSet:
kubectl create -f sematext-agent.yml
- You’re done!
Kubernetes Cheat Sheet
Kubernetes is an open source system for automating deployment, scaling and management of containerized applications that was originally designed by Google and donated to the Cloud Native Computing Foundation. It aims to provide a “platform for automating deployment, scaling, and operations of application containers across clusters of hosts”. It usually works with the Docker container tool and coordinates between a wide cluster of hosts running Docker.