Add structured log for each request that exceeds the configured response time threshold

[Chucks1093]

Summary

Slow requests are currently invisible until they appear in error logs or user reports. A warn-level log for any request exceeding a configurable threshold (default 2000ms) would give operators a proactive signal of performance degradation without requiring external APM tooling.

Scope

• Measure total request duration in the response middleware
• Emit a warn-level log when duration exceeds the threshold with fields: method, path, status_code, duration_ms, wallet (if authenticated), slow_threshold_ms
• Threshold configurable via environment variable SLOW_REQUEST_THRESHOLD_MS (default 2000)
• Log emitted after the response is sent, not before
• Do not log the request body or response body

Acceptance Criteria

• Warn log emitted for requests exceeding the threshold with all six fields
• Threshold configurable via environment variable
• Log emitted after response is sent
• Request and response bodies absent from log
• Fast requests produce no slow-request log entry

ETA: 12 hours

---

Coordinate on Telegram

[k-deejah]

Hello Maintainer,

I’d love to work on this issue. I have experience with backend development and API instrumentation, and I understand the importance of adding useful performance visibility without introducing unnecessary logging overhead or exposing sensitive request data.

I can implement the response-time measurement in the response middleware, add the configurable SLOW_REQUEST_THRESHOLD_MS environment variable with the 2000ms default, and emit a structured warn-level log after the response is sent with the required method, path, status code, duration, threshold, and authenticated wallet fields.

I’ll also ensure request and response bodies are never included, fast requests produce no log entry, and the behavior is covered with appropriate tests.

I can deliver a clean, focused implementation within the 12-hour ETA and coordinate on Telegram as needed.

[grantfox-oss]

🦊 GrantFox — @k-deejah has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #754)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.