Add structured request logging and request IDs #10

Closed
opened 2026-09-04 23:25:59 +02:00 by arne · 0 comments
Owner

Add HTTP request observability using log/slog and a stable request identifier propagated through request context and responses.

Acceptance criteria:

  • Every request has a request ID, preserving a valid inbound ID when appropriate or generating one otherwise.
  • The request ID is available from request context and returned in a response header.
  • Completion logs are structured and include request ID, method, path, status, duration, and response size.
  • Logging middleware preserves optional interfaces required by standard HTTP behavior.
  • Tests cover generated and supplied IDs plus success and error status logging.
  • make check passes.

Dependencies:

  • Depends on #9.
  • Builds on the slog setup from #1.
Add HTTP request observability using `log/slog` and a stable request identifier propagated through request context and responses. Acceptance criteria: - Every request has a request ID, preserving a valid inbound ID when appropriate or generating one otherwise. - The request ID is available from request context and returned in a response header. - Completion logs are structured and include request ID, method, path, status, duration, and response size. - Logging middleware preserves optional interfaces required by standard HTTP behavior. - Tests cover generated and supplied IDs plus success and error status logging. - `make check` passes. Dependencies: - Depends on #9. - Builds on the `slog` setup from #1.
arne closed this issue 2026-09-05 08:16:21 +02:00
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
arne/fjomp#10
No description provided.