Recently, I started using the reverse proxy Traefik [https://traefik.io/] as a default for my projects. Out of the box, Traefik supports Docker Swarm, Kubernetes, and many others. What's unique about Traefik compared to NGINX or Apache is that it dynamically listens to your Orchestrator like Docker and knows
GitHub is full of great code, information, and interesting statistics. GitHub repositories are full of statistics that make perfect candidates to graph with Grafana. The best way to graph this data is of course with Docker and Prometheus. Prometheus contains an impressive list of Exporters [https://prometheus.io/docs/instrumenting/
It's been almost a year since I started the initial Docker Monitoring project [https://github.com/vegasbrianc/docker-monitoring]. This project then spawned off into a Docker Prometheus stack [https://github.com/vegasbrianc/prometheus] shortly after when I discovered the cAdvisor integration. A year is a long time in Open Source
Continuing with the great response from the Docker Monitoring [https://www.brianchristner.io/how-to-setup-docker-monitoring/] post. I am following up by investigating the setup of Prometheus. I first discovered Prometheus while making some changes to the cAdvisor [https://github.com/google/cadvisor] documentation and noticed that cAdvisor now integrates with Prometheus.
Docker monitoring of servers and containers is becoming necessary the more Docker hosts and containers we provision. This tutorial will walk you through how to glue together several different components in order to achieve Docker monitoring. Components for Docker Monitoring First things first. We assume that Docker is installed, configured,