Fix 1Password Connect numeric log levels misclassified in Grafana #287

Merged
eblume merged 2 commits from fix/onepassword-numeric-log-levels into main 2026-03-07 13:57:05 -08:00

2 commits

Author SHA1 Message Date
744255056b Apply same numeric log level fix to alloy-ringtail
1password-connect also runs on ringtail's k3s cluster, so the same
stage.match + stage.template normalization is needed there too.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-07 13:54:18 -08:00
b13ecf05dd Fix 1Password Connect numeric log levels misclassified in Grafana
1Password Connect uses non-standard numeric log levels (1=error..5=trace)
which Grafana can't interpret, causing info-level health checks to appear
as errors. Add a stage.match + stage.template in the Alloy log pipeline
scoped to the 1password namespace to normalize these to standard strings.

See: https://github.com/1Password/connect/issues/44

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-07 13:45:12 -08:00