Open
Description
Motivation
Currently, we have logs on the lambdas for situations where we want to be alerted (like re-orgs with a certain size) but we are not watching for those strings on CloudWatch.
Summary
Since the wallet-service consists of multiple lambdas, we need to add all the logGroups
on log-manager. The problem with doing this manually is that it is very error-prone since we are constantly adding new lambdas to the solution.
There is a potential solution described on this article, we should test it and write a design with a proof of concept to validate it
Another potential solution is to create the subscription filter from the wallet-service project, connecting the logGroups from each wallet-service lambdas to the log-manager
Acceptance Criteria
Guide-level description
Reference-level description
Task Breakdown
Total effort: 1,5 dev days
Task | Effort |
---|---|
Propose a solution for the multiple logGroups issue in log-manager |
1 |
Implement the solution | 0,5 |