Add structured JSON logging across webhook and review flow.

Improve observability with correlation IDs, skip/success/failure lifecycle events, and retry diagnostics while documenting log level configuration. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-06-02 15:00:29 +02:00
parent 7233ab3f32
commit e9aafdf8c4
6 changed files with 125 additions and 26 deletions
@@ -156,6 +156,7 @@ Optional:
 - `MAX_INLINE_COMMENTS` (default: `5`)
 - `REVIEW_TIMEOUT_MS` (default: `120000`)
 - `DEDUPE_TTL_SECONDS` (default: `1800`)
+- `LOG_LEVEL` (default: `info`; options: `debug`, `info`, `warn`, `error`)

 See `.env.example`.

@@ -201,3 +202,4 @@ Post-validation rules:
 - Do not log tokens or raw auth headers.
 - Dedupe is in-memory (resets on restart).
 - Best deployment model is a central service with org-level webhook and per-repo opt-out config.
+- Logs are structured JSON to simplify filtering in Docker/log collectors.