Docker 最佳实战：Docker 部署单节点 Prometheus 实战

cd /data/containers
mkdir -p prometheus/{config,data}
chown nobody.nobody prometheus/data 

# 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: ["192.168.9.81:9090"]

name: "prometheus"
services:
  prometheus:
    image: prom/prometheus:v2.45.5
    container_name: prometheus
    restart: always
    networks:
      - app-tier
    ports:
      - '9090:9090'
    volumes:
      - ./data:/prometheus
      - ./config/prometheus.yml:/etc/prometheus/prometheus.yml
networks:
  app-tier:
    name: app-tier
    driver: bridge
    #external: true

cd /data/containers/prometheus
docker compose up -d

$ docker compose ps
NAME         IMAGE                     COMMAND                  SERVICE      CREATED          STATUS          PORTS
prometheus   prom/prometheus:v2.45.5   "/bin/prometheus --c…"   prometheus   33 seconds ago   Up 32 seconds   0.0.0.0:9090->9090/tcp, :::9090->9090/tcp

# 通过日志查看容器是否有异常，结果略
$ docker compose logs -f