[TT-15354]: Improve logging in JWT Middleware #7528
Merged
probelabs / Visor: connectivity
succeeded
Nov 12, 2025 in 3m 56s
✅ Check Passed (Warnings Found)
connectivity check passed. Found 1 warning, but fail_if condition was not met.
Details
📊 Summary
- Total Issues: 1
- Warning Issues: 1
🐛 Issues by Category
⚡ Performance (1)
⚠️ gateway/mw_jwt.go:986 - The log level for a failed OAuth client lookup has been raised fromDebugtoWarn. This log is on the critical path for every authenticated API request. For common configurations using external Identity Providers, this failure is an expected event. Logging it as a warning for every request can create significant I/O overhead and log volume under high traffic, degrading gateway performance.
Powered by Visor from Probelabs
💡 TIP: You can chat with Visor using /visor ask <your question>
Annotations
Check warning on line 986 in gateway/mw_jwt.go
probelabs / Visor: connectivity
performance Issue
The log level for a failed OAuth client lookup has been raised from `Debug` to `Warn`. This log is on the critical path for every authenticated API request. For common configurations using external Identity Providers, this failure is an expected event. Logging it as a warning for every request can create significant I/O overhead and log volume under high traffic, degrading gateway performance.
Raw output
Revert the log level from `Warnf` back to `Debugf` to avoid performance degradation under high load. A warning for a frequent and expected event in a hot path is not ideal. Consider logging a single warning during API definition loading if a sub-optimal configuration is detected, rather than on every request.
Loading