Skip to content

chore(webhook): enable uvicorn access_log for ingress visibility#77

Merged
max-tet merged 1 commit into
mainfrom
chore/webhook-access-log
May 19, 2026
Merged

chore(webhook): enable uvicorn access_log for ingress visibility#77
max-tet merged 1 commit into
mainfrom
chore/webhook-access-log

Conversation

@ClaydeCode
Copy link
Copy Markdown
Owner

Summary

  • Flip access_log=FalseTrue on the uvicorn Config in orchestrator.py:375.
  • Pebble webhooks fail silently when the request never enqueues (bad token → 401, wrong path → 404, schema mismatch → 422). With access logging off, none of those leave a trace.
  • Today an investigation hit exactly this blind spot: two hours of "webhooks sent, no effect" with zero clayde.pebble.enqueue spans and no log lines either. Cause was unknowable without a request log.

Test plan

  • Rebuild + redeploy container, post a webhook with no auth → expect a 401 line in docker logs clayde-clayde-1.
  • Post a valid webhook → expect a 200 line plus existing [id] enqueued log.
  • Confirm no perf regression (access_log writes are cheap and webhook traffic is low).

🤖 Generated with Claude Code

Without per-request lines, 401/404/422 webhook attempts vanish — no way
to tell if Pebble's posts are arriving with a bad token versus not
arriving at all. Flip access_log on so the next silent-webhook session
leaves a trace.
@max-tet max-tet merged commit 618cbfc into main May 19, 2026
3 checks passed
@max-tet max-tet deleted the chore/webhook-access-log branch May 19, 2026 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants