# Monitoring stack

Prometheus, Grafana, Alertmanager, and application alert rules.

Kubernetes installs `kube-prometheus-stack` in `prometheus` through the deploy
library. Its chart version is pinned there; `k8s/grafana-values.yaml` contains the
values for the whole stack, despite the filename.

The values file is tracked. `.gitignore` also lists it, but that does not stop Git
tracking later edits. Keep local credentials in Secrets rather than treating
changes to this file as ignored.

Prepare Grafana admin and Alertmanager Secrets separately. The Alertmanager
configuration example and Telegram template are in `k8s/`; the main deploy
selection excludes the example config. Certificates and ingress expose Grafana,
and the rule files add service-specific alerts.

The values use `local-path` PVCs for Grafana, Prometheus, and Alertmanager.
Retention is limited by both time and size. Back up Grafana state and any history
that must survive a storage failure.

The Compose stack has separate Prometheus and Alertmanager configuration files.
There is no root active marker. This README describes committed main files;
local VictoriaMetrics experiments are not part of that configuration.

See the [repository README](../README.md) for deployment selection.