0 Fork 0

mirror of https://github.com/ryan4yin/nix-config.git synced 2026-11-13 12:13:36 +01:00

Files

T

Ryan Yin 9b68cfdb8a feat(backup): alert when the last successful backup goes stale

The backup unit publishes `restic_backup_last_success_timestamp_seconds` for the node_exporter textfile collector, and a rejected alert now fails the notify unit instead of exiting 0.

Assisted-by: DeepSeek Harness 0.2.1-rc.2 (deepseek-flash)

2026-10-22 00:54:27 +08:00

argocd-exporter.yml

refactor: rename the three VM hosts to 12kingdoms-*

2026-09-21 17:10:14 +08:00

coredns-exporter.yml

refactor: rename the three VM hosts to 12kingdoms-*

2026-09-21 17:10:14 +08:00

etcd-exporter.yml

refactor: rename the three VM hosts to 12kingdoms-*

2026-09-21 17:10:14 +08:00

fluxcd-exporter.yml

refactor: rename the three VM hosts to 12kingdoms-*

2026-09-21 17:10:14 +08:00

general.yml

refactor: rename the three VM hosts to 12kingdoms-*

2026-09-21 17:10:14 +08:00

istio-exporter.yml

refactor: rename the three VM hosts to 12kingdoms-*

2026-09-21 17:10:14 +08:00

kube-state-metrics-exporter.yml

fix(monitoring): restore youko metrics, alerts and VM-host deploys (#431 )

2026-10-11 18:16:04 +08:00

kubernetes.yml

refactor: rename the three VM hosts to 12kingdoms-*

2026-09-21 17:10:14 +08:00

loki-exporter.yaml

refactor: rename the three VM hosts to 12kingdoms-*

2026-09-21 17:10:14 +08:00

node-exporter.yml

fix(monitoring): alert GPU at 90 C and board sensors at 70 C

2026-10-17 23:14:58 +08:00

nut-exporter.yml

refactor: rename the three VM hosts to 12kingdoms-*

2026-09-21 17:10:14 +08:00

postgres-exporter.yml

fix(monitoring): correct postgres configuration change query

2026-10-17 19:21:22 +08:00

README.md

docs: README audit fixes and de-duplication (#371 )

2026-10-03 18:28:58 +08:00

restic-backup.yml

feat(backup): alert when the last successful backup goes stale

2026-10-22 00:54:27 +08:00

storage.yml

fix(monitoring): stop recurring false alerts (#395 )

2026-10-07 12:51:30 +08:00

README.md

Alert Rules

Alert rules are configurations that define conditions, scope, and actions for generating alerts from monitored signals, such as metrics, logs, or activity. When an alert rule's defined conditions are met for a specific resource within its scope, the system generates a triggered alert, which is the actual instance of the condition being met. These rules specify the data to monitor, the trigger threshold, and the resulting actions, like sending notifications to specific receivers or performing automated tasks.

How these files are loaded

../alert.nix passes every *.yml and *.yaml in this directory to vmalert as a rule file; other extensions are ignored. One rule group per file is easiest to review.