The choice of monitoring systems out there is overwhelming. When I recently needed to set up a monitoring system for a handful of servers, it became clear that many of the go-to solutions like Nagios, Sensu, New Relic would be either too heavy or too expensive – or both. And i found Prometheus and grafana.

The audience is anyone interested in sys-net-ops, netadmin and sysadmin. Attendees can expect to know how to monitoring your server, your application, even docker container.

This presentation aim to cover about how to getting started monitoring your node, virtual machine, application or docker container. What my team really needed was something lean we could spin up in a docker container and then ‘grow’ by extending the configuration or adding components as and when my needs change. With those requirements in hand we soon came across Prometheus, a monitoring system and time series database, with its de-facto graphical front-end Grafana. We're set it up for a trial run and it fit my needs perfectly. The combination of Prometheus and Grafana is becoming a more and more common monitoring stack used by DevOps teams for storing and visualizing time series data. Prometheus acts as the storage backend and Grafana as the interface for analysis and visualization. Prometheus collects metrics from monitored targets by scraping metrics from HTTP endpoints on these targets. But what about monitoring Prometheus itself? Like any server running processes on a host machine, there are specific metrics that need to be monitored such as used memory and storage as well as general ones reporting on the status of the service. Conveniently, Prometheus exposes a wide variety of metrics that can be easily monitored. By adding Grafana as a visualization layer, we can easily set up a monitoring stack for our monitoring stack.

This presentation will help you to understanding what we need to monitoring, and maybe we can help to contribute to the project of the application we used.