Prometheus : Install2022/11/17

	Install Systems monitoring and Alerting toolkit [Prometheus]. Learn Overview about Prometheus on the official site below. ⇒ https://prometheus.io/docs/introduction/overview/
[1]	Set Prometheus repository and Install it. 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.

[root@dlp ~]# cat > /etc/yum.repos.d/prometheus.repo <<'EOF' 
[prometheus]
name=prometheus
baseurl=https://packagecloud.io/prometheus-rpm/release/el/$releasever/$basearch
repo_gpgcheck=1
enabled=1
gpgkey=https://packagecloud.io/prometheus-rpm/release/gpgkey
       https://raw.githubusercontent.com/lest/prometheus-rpm/master/RPM-GPG-KEY-prometheus-rpm
gpgcheck=1
metadata_expire=300
EOF

[root@dlp ~]#

update-crypto-policies --set DEFAULT:SHA1

[root@dlp ~]#

dnf -y install prometheus2 node_exporter

[2]	Configure basic settings on [prometheus.yml].

# the default setting is like follows
# even if keeping default, [Prometheus] server related metrics are collected

[root@dlp ~]#

vi /etc/prometheus/prometheus.yml

# my global config
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).

# Alertmanager configuration
alerting:
  alertmanagers:
  - static_configs:
    - targets:
      # - alertmanager: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'

    # metrics_path defaults to '/metrics'
    # scheme defaults to 'http'.

    static_configs:
    - targets: ['localhost:9090']

  # add : grab stats about the local machine by [node-exporter]
  - job_name: node
    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. It's also possible to input queries directly on the input form above, by Prometheus [Expression Language]. Refer to the official document about usage of Expression Language. ⇒ https://prometheus.io/docs/querying/examples/

[6]	This is the state of executing [node_load1].

[7]	To click [Status] - [Targets], possible to confirm status for each node.

Matched Content