Trey t c845771946 feat(observability): drop health/metrics probe noise from shipped logs ...

The api logs every request, so k8s liveness/readiness probes on
/api/health/ and vmagent's /metrics scrape drowned Loki in 2xx access
logs. Alloy now drops successful probe/scrape access lines at ingest
(loki.process stage.drop) — a non-2xx health check, or one logged
above info level, still matches nothing and is kept.

Also hardens Alloy's read-offset store: moved /tmp/alloy from an
emptyDir to a hostPath and set loki.source.file tail_from_end=true, so
a pod restart resumes from the saved offset instead of re-reading log
files from the start — which made Loki 400-reject the now-too-old
entries ("entry too far behind") and stalled shipping.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-17 21:29:15 -05:00

..

alloy-logs.yaml

feat(observability): drop health/metrics probe noise from shipped logs

2026-05-17 21:29:15 -05:00

kube-state-metrics.yaml

fix(observability): unbreak vmagent SD on fresh deploy + ship kube-state-metrics

2026-05-13 00:30:11 -05:00

vmagent.yaml

fix(security): remediate 2026-05-12 audit findings (Stages 2–5)

2026-05-16 22:28:33 -05:00