๐ ๐๐จ๐ง๐ข๐ญ๐จ๐ซ๐ข๐ง๐ & ๐๐จ๐ ๐ ๐ข๐ง๐ ๐๐ฎ๐๐๐ซ๐ง๐๐ญ๐๐ฌ ๐ฐ๐ข๐ญ๐ก ๐๐๐ ๐๐ง๐ ๐ ๐ข๐ฅ๐๐๐๐๐ญ ๐
Logging is a critical tool/process for monitoring application(s) behaviour in the world of Kubernetes. Itโs the heartbeat that ensures smooth operations, allowing timely detection and resolution of issues critical for production workloads.
It is really important to understand Kubernetes logging as it helps in effective troubleshooting and mitigating application issues that may arrive later.
In the below GIF, I used the Kubernetes SideCar approach for effective logging and monitoring.
More on Kubernetes logging and Side Car approach: https://kubernetes.io/docs/concepts/cluster-administration/logging/
๐๐ก๐ ๐๐ข๐๐๐๐๐ซ ๐๐ฉ๐ฉ๐ซ๐จ๐๐๐ก ๐๐ฌ๐ฌ๐ข๐ ๐ง๐ฌ ๐ ๐๐๐๐ข๐๐๐ญ๐๐ ๐ฅ๐จ๐ ๐ ๐ข๐ง๐ ๐๐ ๐๐ง๐ญ ๐ญ๐จ ๐๐๐๐ก ๐๐๐. It uses more resources but offers flexibility and isolation, making it ideal for sizable K8s clusters or clusters supporting multiple business entities like PAAS platforms.
๐ /Log/xxx โ Pods on worker nodes put their stories in a dedicated log directory, plain and simple.
๐ข Filebeat Container (Logging agent) โ Every POD has it, snatching those logs from application containers. It takes logs and ships them to Logstash forโฆ
