centralized logging #4
Merged
Conversation
This file contains 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
- set invoke settings to 0 retries and 6 hour max event age - fixed misspellings - removed deployment_name variable
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.
Purpose
The purpose of this PR is to implement a centralized CloudWatch log group to allow for the aggregation of disparate logs from the initiator, trigger, and evaluator lambda functions. Having their logs recorded to a centralized log group allows users to view and search logged events sorted by time and provides a one-stop shop for debugging requests along a pipeline.
Proposed Changes
Issues
Testing
https://drive.google.com/file/d/1gmrzsUrw5RAS2ucbE8GTe1t8QrsbyKrQ/view?usp=drive_link