I Added Log Aggregation to My EKS Observability Stack, Metrics + Logs in One Dashboard
Last week I built an observability stack with Prometheus, Grafana, and custom alerting on EKS. The LinkedIn post got more engagement than anything I'd posted before, and two comments suggested the ...

Source: DEV Community
Last week I built an observability stack with Prometheus, Grafana, and custom alerting on EKS. The LinkedIn post got more engagement than anything I'd posted before, and two comments suggested the same thing: "Integrate Loki for logs." They were right. Metrics tell you that something is wrong. Logs tell you why. Without both in the same place, you're switching between kubectl logs and Grafana dashboards trying to correlate timestamps manually. That's not a workflow, that's a scavenger hunt. So I added Loki. What I Added Loki and Promtail, deployed via ArgoCD alongside the existing Prometheus stack: Promtail runs as a DaemonSet on every node, tailing container logs from /var/log/pods Loki stores and indexes the logs, queryable via LogQL Grafana gets a new "Logs & Metrics Correlation" dashboard with metrics and logs side by side A new Loki datasource in Grafana so both Prometheus and Loki are available in the same dashboard The entire addition was three files: an ArgoCD application f