Implement a pattern for compliant logging to CloudWatch Logs#260
Draft
Implement a pattern for compliant logging to CloudWatch Logs#260
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
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.
Description of the Change
We have developed a series of logging guidelines at Thunderbird, and we have described how CloudWatch Logs can implement those guidelines. This PR is the real implementation of what is described in that document.
Benefits
We'll have a way of stamping out log destinations throughout our projects, knowing they'll be compliant with our policies. If our policies change, we'll have a centralized place to implement those changes across projects.
Applicable Issues
See #258.