Files
DongHyeonka 414d62b315 refactor(postgres): keep the backup alerts with the backup
The observability core renderer rejects any alert or record whose
name contains "backup" (no_unscoped_monitors_rules): backup
monitoring is outside the observability core by design. 90ab8f4 put
PlatformPostgresBackupMissing and PlatformPostgresWALArchiveBacklog in
core-rules.yaml, so the pinned renderer failed with "out-of-scope
monitor or rule is present".

Move both alerts unchanged into
services/platform-postgres-backup/prometheus-rule.yaml in
platform-data, which Prometheus reads because the namespace has
observability.hyeonworks.com/enabled=true and the rule has
observability.hyeonworks.com/instance=home. They now point their
runbook_url at the backup README and are applied with the
ScheduledBackup. Renaming them to dodge the filter was rejected: it
would keep backup rules inside a scope that excludes them on purpose.

Verification: test-platform-disk-alerts.sh loads both rule files and
passes; promtool checks 13 rules. render-observability-core.sh and
test-render-observability-core.sh pass, and kubectl apply
--dry-run=server accepts the backup kustomization with the rule.
scan-platform-sensitive-source.sh stops at its observability-core
renderer with RC=23 here and on an origin/main snapshot alike, so it
says nothing about this change.

Fixes: 90ab8f4e65 ("feat(postgres): back up platform-postgres to AIStor every day")
2026-11-12 07:25:25 +09:00
..

Observability core

This root composes the internal observability workloads deployed after the namespace, CRD, and Local PV prerequisites:

  • kube-prometheus-stack without Grafana or its bundled node-exporter;
  • single-binary Loki and Tempo using isolated AIStor buckets;
  • Alloy for Pod logs and internal OTLP/gRPC traces;
  • a standalone node-exporter;
  • the exact core NetworkPolicy matrix, platform rules, scrape targets, verified dashboards, and source-only Alertmanager Slack routing.

It intentionally does not create public ingress, Grafana, OIDC, or credential Secrets. The Slack routing source references alertmanager-slack-webhook/url; while that Secret is absent, do not apply the AlertmanagerConfig, its kube-prometheus-stack reference, its public HTTPS NetworkPolicy, or alert rules. Namespace, CRD, and Local PV roots remain outside this aggregate because their protected apply order is different.