Files
ERP/monitoring/docker-compose.monitoring.yml
T
whqreza 887a3af84f refactor(monitoring): move grafana into the main compose stack
Owner request: one 'docker compose up -d' should bring the whole system up —
no separate monitoring project to start for the dashboards.

- docker-compose.yml: grafana service (procurement-grafana, loopback :3001,
  default+shared networks, obs datasource env) + grafana_data volume;
  provisioning and dashboard JSONs stay in ./monitoring/grafana/ (no file
  moves, provisioning unchanged)
- docker-compose.prod.yml: GRAFANA_ADMIN_PASSWORD forced via the existing
  ${VAR:?} pattern (local keeps a lenient default, prod refuses defaults)
- monitoring/docker-compose.monitoring.yml: grafana service + volume removed
  (no name/port conflict); glitchtip/prometheus/loki stay server-side as before
- docs updated: grafana restarts on app deploys are harmless (settings live
  in the volume); SSH-tunnel posture unchanged

Verified locally: both compose files validate; 'docker compose up -d' starts
all 10 services incl. procurement-grafana; BotPostgres datasource health OK;
all 3 dashboards provisioned in the fresh volume; monitoring compose no
longer contains grafana; old monitoring-grafana container removed; port
still loopback-only.
2026-10-27 01:43:31 +03:30

185 lines
6.5 KiB
YAML

# ============================================================================
# Monitoring stack — SEPARATE compose project from the ERP app on purpose:
# app rebuilds (push-to-deploy) must never restart monitoring containers.
#
# cd /srv/erp # repo root, so --env-file picks up the app's .env
# docker compose -f monitoring/docker-compose.monitoring.yml --env-file .env up -d
#
# Included (≈2.2 GB RAM budgeted):
# GlitchTip (errors, Sentry-compatible) + its own small Postgres
# Prometheus (metrics) + Grafana (dashboards) + Loki/Promtail (logs)
# node-exporter (host) + postgres-exporter (app DB) + cAdvisor (containers)
#
# Admin UIs (Grafana :3001, GlitchTip :8001) bind to 127.0.0.1 only —
# reach them via SSH tunnel exactly like the MinIO console. GlitchTip ALSO
# needs a public origin for the browser SDK: set GLITCHTIP_HOST and enable
# the "public" profile (Traefik route + TLS) — see monitoring/README.md.
# ============================================================================
services:
# ---------------------------------------------------------------- errors --
glitchtip:
image: glitchtip/glitchtip:latest # pinned upstream: version tags are dated, keep an eye on updates
container_name: monitoring-glitchtip
mem_limit: 640m
environment:
SECRET_KEY: ${GLITCHTIP_SECRET_KEY:?set GLITCHTIP_SECRET_KEY in .env}
GLITCHTIP_DOMAIN: ${GLITCHTIP_DOMAIN:?set GLITCHTIP_DOMAIN in .env}
DATABASE_URL: postgres://glitchtip:${GLITCHTIP_DB_PASSWORD:-glitchtip}@glitchtip-postgres:5432/glitchtip
# Single-container mode (embedded worker) — no redis needed at this scale.
GLITCHTIP_EMBED_WORKER: "true"
VALKEY_URL: ""
ENABLE_USER_REGISTRATION: "false"
ENABLE_ORGANIZATION_CREATION: "false"
DEFAULT_FROM_EMAIL: ${GLITCHTIP_FROM_EMAIL:-noreply@bennu-api-bahrestan.ir}
EMAIL_URL: ${GLITCHTIP_EMAIL_URL:-consolemail://}
ports:
- "127.0.0.1:8001:8000"
depends_on:
glitchtip-postgres:
condition: service_healthy
networks:
- monitoring
- shared
- traefik # public DSN route (profile "public")
labels:
- traefik.enable=true
- traefik.http.routers.glitchtip.rule=Host(`${GLITCHTIP_HOST:-errors.localhost}`)
- traefik.http.routers.glitchtip.entrypoints=web
- traefik.http.services.glitchtip.loadbalancer.server.port=8000
restart: unless-stopped
glitchtip-postgres:
image: postgres:16-alpine
container_name: monitoring-glitchtip-postgres
mem_limit: 128m
environment:
POSTGRES_DB: glitchtip
POSTGRES_USER: glitchtip
POSTGRES_PASSWORD: ${GLITCHTIP_DB_PASSWORD:-glitchtip}
volumes:
- glitchtip_postgres_data:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U glitchtip -d glitchtip"]
interval: 10s
timeout: 5s
retries: 10
networks:
- monitoring
restart: unless-stopped
# --------------------------------------------------------------- metrics --
prometheus:
image: prom/prometheus:v3.4.1
container_name: monitoring-prometheus
mem_limit: 512m
command:
- --config.file=/etc/prometheus/prometheus.yml
- --storage.tsdb.retention.time=14d
- --storage.tsdb.retention.size=2GB
volumes:
- ./prometheus:/etc/prometheus:ro
- prometheus_data:/prometheus
networks:
- monitoring
- shared
restart: unless-stopped
# ------------------------------------------------------------------ logs --
# NOTE (2026-10-25): the grafana service MOVED to the main docker-compose.yml
# (owner decision: one `docker compose up -d` brings the app + grafana up
# together). It still reads its provisioning + dashboards from
# ./monitoring/grafana/ — see the main compose file for env/ports.
loki:
image: grafana/loki:3.5.0
container_name: monitoring-loki
mem_limit: 384m
command: -config.file=/etc/loki/loki-config.yml
volumes:
- ./loki/loki-config.yml:/etc/loki/loki-config.yml:ro
- loki_data:/loki
networks:
- monitoring
restart: unless-stopped
promtail:
image: grafana/promtail:3.5.0
container_name: monitoring-promtail
mem_limit: 64m
command: -config.file=/etc/promtail/promtail-config.yml
volumes:
- ./promtail/promtail-config.yml:/etc/promtail/promtail-config.yml:ro
- /var/lib/docker/containers:/var/lib/docker/containers:ro
- /var/run/docker.sock:/var/run/docker.sock:ro
networks:
- monitoring
restart: unless-stopped
# -------------------------------------------------------------- exporters --
# Linux-host only (see cadvisor note): local runs skip it via the profile.
node-exporter:
image: prom/node-exporter:v1.9.1
container_name: monitoring-node-exporter
mem_limit: 32m
profiles: ["host-metrics"]
command:
- --path.rootfs=/host
volumes:
- /:/host:ro,rslave
pid: host
networks:
- monitoring
restart: unless-stopped
postgres-exporter:
image: prometheuscommunity/postgres-exporter:v0.17.1
container_name: monitoring-postgres-exporter
mem_limit: 48m
environment:
# App database on the main stack's postgres (reaches it via erp_shared).
DATA_SOURCE_NAME: postgres://postgres:${POSTGRES_PASSWORD:?set POSTGRES_PASSWORD in .env}@postgres:5432/procurement?sslmode=disable
networks:
- monitoring
- shared
restart: unless-stopped
# Linux-host only: the rootfs bind mounts fail on Docker Desktop (Windows/macOS).
# VPS: docker compose -f monitoring/docker-compose.monitoring.yml --env-file .env \
# --profile host-metrics up -d
# Local: started WITHOUT the profile — per-container metrics are simply absent.
cadvisor:
image: gcr.io/cadvisor/cadvisor:v0.49.1
container_name: monitoring-cadvisor
mem_limit: 128m
profiles: ["host-metrics"]
privileged: true
devices:
- /dev/kmsg
volumes:
- /:/rootfs:ro
- /var/run:/var/run:ro
- /sys:/sys:ro
- /var/lib/docker/:/var/lib/docker:ro
networks:
- monitoring
restart: unless-stopped
networks:
monitoring:
driver: bridge
# Reaches the ERP containers (api:8000/metrics, postgres:5432) — the main
# compose declares the same fixed-name network as "shared".
shared:
name: erp_shared
external: true
# Created by the main compose; required only for the public GlitchTip route.
traefik:
name: traefik_network
external: true
volumes:
glitchtip_postgres_data:
prometheus_data:
loki_data: