Raspberry-Pi-IaC/roles/monitoring/vars/main/defaults.yml
Thomas Kleinendorst 71499b2610 Bind hostname to 172.0.1.1 and use FQDN in config
This makes that we see better labels in Grafana and that we don't
need to expose the address externally.
2024-09-23 12:23:05 +02:00

55 lines
1.6 KiB
YAML

---
# Prometheus
prometheus_version: "2.54.1"
prometheus_targets:
prometheus:
- targets:
- raspberry-pi-1.kleinendorst.info:9090
node:
- targets:
- raspberry-pi-1.kleinendorst.info:9100
grafana:
- targets:
- raspberry-pi-1.kleinendorst.info:3000
prometheus_web_listen_address: 127.0.0.1:9090
prometheus_scrape_configs:
- job_name: "prometheus"
file_sd_configs:
- files:
- "{{ prometheus_config_dir }}/file_sd/prometheus.yml"
- job_name: "node"
file_sd_configs:
- files:
- "{{ prometheus_config_dir }}/file_sd/node.yml"
- job_name: "grafana"
file_sd_configs:
- files:
- "{{ prometheus_config_dir }}/file_sd/grafana.yml"
prometheus_alertmanager_config:
- static_configs:
- targets:
- raspberry-pi-1.kleinendorst.info:9093
# Node exporter
node_exporter_version: "1.8.2"
node_exporter_enabled_collectors:
- systemd
- {"textfile": {"directory": "{{ node_exporter_textfile_dir }}"}}
- processes
node_exporter_web_listen_address: 127.0.0.1:9100
# Alertmanager
alertmanager_version: "0.27.0"
alertmanager_web_listen_address: 127.0.0.1:9093
# Telegram configuration inspired by this source:
# https://www.stranatesta.eu/tech/how-to-configure-prometheus-alertmanager-to-send-alerts-to-telegram/#configure-alertmanager
alertmanager_receivers:
- name: telegram
telegram_configs:
- bot_token: "{{ telegram_bot_token }}"
api_url: 'https://api.telegram.org'
chat_id: "{{ telegram_chat_id }}"
parse_mode: ''
alertmanager_route:
receiver: telegram
# Grafana
grafana_version: "11.2.0"
grafana_username: grafana