Change non-fatal API error logs from Warn to Debug #96
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.
Summary
Changes these logs from Warn to Debug level:
sso_user.go:67- "failed to get user status from scim"iam_user.go:153- "Error listing access keys"iam_user.go:161- "Error getting access key last used"Why
These are non-fatal errors that don't block sync - we continue processing other users/keys. The code handles these errors gracefully (falls back to default values) and sync completes successfully.
Since these errors are expected in certain conditions (permission issues, access key configurations) and don't impact sync outcomes, Debug level is more appropriate.
Combined these were generating ~19K warn logs per 6 hours in production.
Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.