[log] Add debug logging to guard registry #330
Merged
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
Enhanced
internal/guard/registry.gowith debug logging for better troubleshooting and development visibility.Changes Made
guard:registryfollowing project conventionsNewRegistry()- Logs registry creationRegister()- Logs guard registration with server ID and guard nameGet()- Logs guard retrieval attempts and resultsRemove()- Logs guard removal operationsCreateGuard()- Logs guard factory operations with type resolutionDebug Logging Features
All debug logs:
DEBUG=guard:*orDEBUG=*pkg:filenamenaming conventionTesting
Enable debug logging with:
DEBUG=guard:* ./awmg --config config.tomlCompliance
✅ Single file modified (focused PR)
✅ No test files modified
✅ Logger naming follows
pkg:filenameconvention✅ No side effects in log arguments
✅ Meaningful log messages for debugging
✅ No duplicate logging with existing logs
✅ Proper import formatting