ddadmin e851ef9788 fix(monitoring): add recover flow for stuck monitoring stack ...

- Why:
  - during intensive development monitoring can get stuck (No data, out of bounds)
  - regular reload is not always enough to recover Prometheus + StatsD pipeline
- What:
  - add make target recover-monitoring for hard recovery path
  - recreate prometheus and statsd-exporter, restart airflow scheduler/webserver
  - keep Grafana provisioning reload and target checks in one command
  - document when to use recover-monitoring in OPERATIONS runbook
- Check:
  - run make recover-monitoring
  - verify Prometheus targets for airflow/clickhouse/kafka are up

2026-02-09 09:28:13 +03:00

..

ARCHITECTURE.md

refactor(airflow): move DAGs to airflow/dags and update paths

2026-02-08 19:34:10 +03:00

COMMIT_RULES.md

docs(docs): clarify multiline commit body usage

2026-02-08 20:49:18 +03:00

DE-task.md

fix(infra): harden grafana permissions and document recovery

2026-02-08 21:38:23 +03:00

OPERATIONS.md

fix(monitoring): add recover flow for stuck monitoring stack

2026-02-09 09:28:13 +03:00

REPO_MAP.md

docs(repo-map): add monitoring configs and plans

2026-02-08 22:33:01 +03:00