2017-07-27 08:51:35 -07:00
# Grafana Dashboards
2017-07-27 08:39:53 -07:00
2023-12-09 05:58:02 -08:00
## Node Exporter Full
2017-07-27 08:51:35 -07:00
2023-12-09 06:13:35 -08:00
- For node_exporter
- Monitor Linux system.
2018-05-25 03:28:53 -07:00
2023-12-09 06:08:21 -08:00
Only requires the default job_name: node, add as many targets as you need in `/etc/prometheus/prometheus.yml` .
2017-07-27 08:39:53 -07:00
2023-12-09 05:58:53 -08:00
```yaml
2017-07-27 08:39:53 -07:00
- job_name: node
static_configs:
- targets: ['localhost:9100']
2017-07-27 08:41:22 -07:00
```
2017-07-27 08:51:35 -07:00
2023-12-09 06:08:21 -08:00
Recommended for prometheus-node-exporter the arguments `--collector.systemd` and `--collector.processes` because the graph uses some of their metrics.
2020-05-22 10:30:55 -07:00
2023-12-09 06:22:39 -08:00
> - `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](http://pcp.io) for document the values reported > by the kernel in `/proc` (in their `/pmdas/linux/help` src file mainly).
2017-09-15 08:41:57 -07:00
2017-07-27 08:51:35 -07:00
2023-12-09 05:58:02 -08:00
## Node Exporter FreeBSD
2018-03-24 01:39:02 -07:00
2023-12-09 06:13:35 -08:00
- For node_exporter in FreeBSD system
- Monitor FreeBSD system.
2018-05-25 03:28:53 -07:00
2023-12-09 06:13:35 -08:00
Only requires a configured target under any `job_name` .
2018-03-24 01:39:02 -07:00
2023-12-09 06:08:21 -08:00
## Haproxy Full _(deprecated)_
2017-07-27 08:51:35 -07:00
2023-12-09 06:13:35 -08:00
- For haproxy_exporter
- Monitor Haproxy service.
2017-07-27 08:51:35 -07:00
2023-12-09 06:13:35 -08:00
Only requires a configured target under any `job_name` .
2017-07-31 09:27:56 -07:00
2023-12-09 05:58:02 -08:00
## Haproxy 2 Full
2019-05-18 10:47:19 -07:00
2023-12-09 06:13:35 -08:00
- For Haproxy compiled with Prometheus support
- Monitor Haproxy service direct.
2019-05-18 10:47:19 -07:00
2023-12-09 06:13:35 -08:00
Only requires a configured target under any `job_name` .
2019-05-18 10:47:19 -07:00
2023-12-09 05:58:02 -08:00
## Apache Full
2017-09-15 08:41:57 -07:00
2023-12-09 06:13:35 -08:00
- Monitor Apache service.
2018-05-25 03:28:53 -07:00
2023-12-09 06:08:21 -08:00
> Moved to https://github.com/grafana/jsonnet-libs
2017-09-15 08:41:57 -07:00
2018-05-25 03:28:53 -07:00
2023-12-09 05:58:02 -08:00
## NFS Full
2018-05-25 03:28:53 -07:00
2023-12-09 06:13:35 -08:00
- For node_exporter
- Monitor all NFS and NFSd exported values.
2018-05-25 03:28:53 -07:00
2023-12-09 06:08:21 -08:00
Check that the process was started with the arguments `--collector.nfs` and `--collector.nfsd` .
2018-05-25 03:28:53 -07:00
2023-12-09 06:21:58 -08:00
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` .
2018-05-25 03:28:53 -07:00
2020-04-24 10:40:51 -07:00
2023-12-09 06:08:21 -08:00
## BIND 9 Full
2020-04-24 10:40:51 -07:00
2023-12-09 06:13:35 -08:00
- For [prometheus-bind-exporter ](https://github.com/prometheus-community/bind_exporter )
- Monitor BIND 9 service.
Required configuration in `/etc/bind/named.conf.options` :
2020-04-24 10:40:51 -07:00
2023-12-09 05:58:53 -08:00
```c++
2020-04-25 06:12:33 -07:00
statistics-channels {
inet 127.0.0.1 port 8053 allow { 127.0.0.1; };
};
```
2020-04-24 10:40:51 -07:00
2023-12-09 06:08:21 -08:00
On Grafana, it only requires a configured target under any `job_name` . For example:
2020-04-24 10:40:51 -07:00
2023-12-09 05:58:53 -08:00
```yaml
2020-04-24 10:40:51 -07:00
- job_name: 'bind'
static_configs:
- targets:
2023-05-03 05:29:11 -07:00
- server_hostname:9000
2020-04-24 10:40:51 -07:00
```