381816a66e1f59f196cee5a8f14c4249dc144789
schemas / vulnerabilities (pull_request) Successful in 1m49s
schemas / check (pull_request) Successful in 3m5s
schemas / check-release (pull_request) Successful in 3m45s
pre-commit / pre-commit (pull_request) Successful in 6m15s
schemas / build (pull_request) Successful in 5m51s
schemas / deploy-prod (pull_request) Has been skipped
When start() returns an error, main() logged it via the slog logger and returned normally (exit 0), so a crash-looping pod showed as "Completed" with no error in the logs: start() defers the OTel SDK shutdown, tearing down the log exporter before main() logs, so with LOG_FORMAT=otel the record never reaches Alloy. Also write the error to stderr (always captured by `kubectl logs`) and os.Exit(1) so the container is correctly reported as failed.
Description
No description provided