[Feature]: add structured application logger - #112
Merged
Conversation
Signed-off-by: viiccwen <vicwen@apache.org>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Add a shared JSON Lines application logger with consistent event fields and default redaction or hashing for sensitive values. Migrate the notification service as the initial structured-logging slice while preserving stderr and Docker log compatibility.
Related Issue
Fixes #90
Type of Change
Changes
Testing
make test(257 passed)make precommitandgit diff --checkImpact Checklist
Notes for Reviewers
Issue #90 intentionally requests a small initial migration slice. This PR migrates the complete
notificationsmodule; remaining application logs can move incrementally under the broader observability work in #89.