Prometheus : Install2026/03/26 |
|
Install Systems monitoring and Alerting toolkit [Prometheus].
Learn Overview about Prometheus on the official site below. |
|
| [1] | Install Prometheus. Install Prometheus Server and also Install [node-exporter] that includes features to get metric data of general resource on the System like CPU or Memory usage. |
|
# install from EPEL [root@dlp ~]# dnf --enablerepo=epel -y install prometheus node-exporter
|
| [2] | Configure basic settings on [prometheus.yml]. |
|
# the default setting is like follows # even if keeping default for localhost, [Prometheus] server related metrics are collected [root@dlp ~]# vi /etc/prometheus/prometheus.yml
global:
scrape_interval: 15s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
# scrape_timeout is set to the global default (10s).
# Attach these labels to any time series or alerts when communicating with
# external systems (federation, remote storage, Alertmanager).
external_labels:
monitor: 'example'
# Alertmanager configuration
alerting:
alertmanagers:
- static_configs:
- targets: ['localhost:9093']
# Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
rule_files:
# - "first_rules.yml"
# - "second_rules.yml"
# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
# The job name is added as a label `job=<job_name>` to any timeseries scraped from this config.
- job_name: 'prometheus'
# Override the global default and scrape targets from this job every 5 seconds.
scrape_interval: 5s
scrape_timeout: 5s
# metrics_path defaults to '/metrics'
# scheme defaults to 'http'.
static_configs:
- targets: ['localhost:9090']
- job_name: node
# If prometheus-node-exporter is installed, grab stats about the local
# machine by default.
static_configs:
- targets: ['localhost:9100']
[root@dlp ~]# systemctl enable --now prometheus node_exporter
|
| [3] | If Firewalld is running, allow services. |
|
[root@dlp ~]# firewall-cmd --add-service=prometheus success [root@dlp ~]# firewall-cmd --runtime-to-permanent success |
| [4] | Access to the [http://(Prometheus server's hostname or IP address):9090/] from a client computer, Then, Prometheus Web UI is shown like follows. |
|
| [5] |
To click [Metrics Exporter], there are many queries to view time series data. ⇒ https://prometheus.io/docs/querying/examples/ |
|
| [6] | This is the state of executing [node_load5]. |
|
| [7] | To click [Status] - [Targets], possible to confirm status for each node. |
|
| Sponsored Link |
|
|