Monitoring with Node Exporter and cAdvisor | Prometheus Advanced Features

Monitoring with Node Exporter and cAdvisor Prometheus Advanced Features
Prometheus Advanced Features | Monitoring Linux Host with Node Exporter | Docker Container Monitoring using cAdvisor
In this lecture, you will learn Monitoring Linux Host Metrics with Node Exporter, Monitoring Docker container Metrics using cAdvisor, Making Prometheus Highly Available and Scaling Prometheus Deployments
Node Exporter
For well-known applications, servers, or databases, Prometheus/Community have built exporters that you can use to monitor your targets. Exporters are basically any scripts or services that fetch specific metrics from your system and then give data in Prometheus format. This is the main way of monitoring targets with Prometheus. Node Exporter is a Prometheus exporter that exposes hardware- and kernel-related metrics. Therefore, you can use Node Exporter to monitor filesystems, disks, CPUs and network statistics of your computer system.
The cAdvisor
Container Advisor provides an understanding of the resource usage and performance characteristics of running containers. It is a daemon that collects, aggregates, processes, and exports information about running containers. Specifically, for each container, it keeps resource isolation parameters, historical resource usage, histograms of complete historical resource usage and network statistics. This data is exported by container and machine-wide. It has native support for Docker containers.
Initial HA Prometheus
For most people already operating in the Kubernetes world, the typical way of getting Prometheus to be HA is Simply to use Kubernetes itself i.e to have multiple instances of Prometheus and to deploy it into Kubernetes, so that Kubernetes can manage the temporary loss of infrastructure. This approach however still leaves some problems unsolved:
Data Retention
Prometheus will only keep a small window of data – if you want to review historical data to see what the system was doing last week/month/etc, you can’t.
Data Inconsistency
Just putting a load balancer in front of multiple Prometheus assumes that all of them were up and able to scrape the same metrics – a new instance starting up will have no historical data.
Hidden Outages
If Prometheus is supposed to be monitoring Kubernetes, then there is the potential problem of an outage on Kubernetes not being reported because Prometheus wasn’t up to notice it.
The third problem can be solved using autoscaling type functionality.
docker installation,node exporter,node exporter docker,node exporter prometheus grafana,node cadvisor,node exporter tutorial,node exporter linux,docker node exporter,node exporter metrics,node exporter dashboard,cadvisor,cadvisor install,cadvisor tutorial,monitoring with cadvisor,cadvisor metrics explained,cadvisor docker monitoring,cadvisor setup,cadvisor docker,#docker cadvisor
*Connect with me*

👩🎓*My Courses - Message me at LinkedIN for discounts**