Fix Alloy logfmt decode errors for JSON logs #46

Merged

eblume merged 1 commit from feature/fix-alloy-logfmt-errors into main

2026-01-22 18:00:35 -08:00

eblume commented

2026-01-22 17:59:51 -08:00

Owner

Summary

Use stage.match to conditionally apply logfmt parsing only to lines that don't start with {
This prevents error spam like "failed to decode logfmt" component_path=/ component_id=loki.process.pods component=stage type=logfmt err="logfmt syntax error at pos 2 on line 1: unexpected '\"'" when JSON-formatted logs hit the logfmt parser

Deployment and Testing

Sync alloy-k8s app to feature branch and verify errors stop appearing
Verify JSON logs are still parsed correctly
Verify logfmt logs (from Loki, Prometheus etc.) are still parsed correctly

🤖 Generated with Claude Code

## Summary - Use `stage.match` to conditionally apply logfmt parsing only to lines that don't start with `{` - This prevents error spam like `"failed to decode logfmt" component_path=/ component_id=loki.process.pods component=stage type=logfmt err="logfmt syntax error at pos 2 on line 1: unexpected '\"'"` when JSON-formatted logs hit the logfmt parser ## Deployment and Testing - [ ] Sync alloy-k8s app to feature branch and verify errors stop appearing - [ ] Verify JSON logs are still parsed correctly - [ ] Verify logfmt logs (from Loki, Prometheus etc.) are still parsed correctly 🤖 Generated with [Claude Code](https://claude.com/claude-code)

eblume added 1 commit

2026-01-22 17:59:51 -08:00

Fix Alloy logfmt decode errors for JSON logs 13b21b09f2

Use stage.match to conditionally apply logfmt parsing only to lines
that don't start with '{'. This prevents error spam when JSON-formatted
logs are passed to the logfmt parser.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>