feat: add logging for error conditions and edge cases #734
+58
−7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add warning-level logging when health probes fail or 503 responses are returned, providing visibility into why checks are failing (config not loaded vs database connectivity issues).
Add debug/warning logs to improve observability: - Token validation failures (security audit) - IAM communication errors in auth flows - Token revocation failures with context - Database connection failures - Device flow code collisions - Header parsing failures - Uvicorn logger configuration issues
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add debug/warning logs for better observability of auth failures, DB connection issues, and edge cases.