- For node_exporter
- Monitor Linux system.
Only requires the default job_name: node, add as many targets as you need in /etc/prometheus/prometheus.yml
.
- job_name: node
static_configs:
- targets: ['localhost:9100']
Recommended for prometheus-node-exporter the arguments --collector.systemd
and --collector.processes
because the graph uses some of their metrics.
timeInterval
in the Grafana data source has to be set accordingly to the >scrape_interval
configured in Prometheus- For prometheus-node-exporter v.0.16 or older, use
node-exporter-full-old.> json
- Thanks to the PCP project for document the values reported > by the kernel in
/proc
(in their/pmdas/linux/help
src file mainly).
- For node_exporter in FreeBSD system
- Monitor FreeBSD system.
Only requires a configured target under any job_name
.
- For haproxy_exporter
- Monitor Haproxy service.
Only requires a configured target under any job_name
.
- For Haproxy compiled with Prometheus support
- Monitor Haproxy service direct.
Only requires a configured target under any job_name
.
- Monitor Apache service.
- For node_exporter
- Monitor all NFS and NFSd exported values.
Check that the process was started with the arguments --collector.nfs
and --collector.nfsd
.
The same as Node Exporter Full. Only requires the default job_name: node
, add as many targets as you need in /etc/prometheus/prometheus.yml
.
- For prometheus-bind-exporter
- Monitor BIND 9 service.
Required configuration in /etc/bind/named.conf.options
:
statistics-channels {
inet 127.0.0.1 port 8053 allow { 127.0.0.1; };
};
On Grafana, it only requires a configured target under any job_name
. For example:
- job_name: 'bind'
static_configs:
- targets:
- server_hostname:9000