Ability for `Logger` to ship logs to CloudWatch Logs
See original GitHub issueIs your feature request related to a problem? Please describe. As a developer, I would like for Amplify to support log shipping to CloudWatch logs via the use of Logger. So I can send certain logs (like errors or stack traces) to my AWS account for future analysis.
Describe the solution you’d like
This feature would leverage the Cognito integration such that log shipping is done in a secure fashion with temporary credentials. I would like for the Logger
to take care of sending logs in batches in the background and support a local cache for lost connectivity.
Describe alternatives you’ve considered I have considered using existing npm packages like https://www.npmjs.com/package/winston-cloudwatch.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:67
- Comments:31 (6 by maintainers)
Top Results From Across the Web
Send logs to CloudWatch Logs - AWS Documentation
To send logs from your containers to Amazon CloudWatch Logs, you can use Fluent Bit or Fluentd. For more information, see Fluent Bit...
Read more >cloudwatch_logger - ROS Wiki
The cloudwatch_logger node enables logs generated in a ROS system to get sent to Amazon CloudWatch Logs. Out of the box, this node...
Read more >Implement these 4 Amazon CloudWatch Logs best practices
Examine best practices for using Amazon CloudWatch Logs, which gives IT admins a set of tools to monitor and analyze cloud applications.
Read more >AWS Log Analysis via CloudWatch Logs Insights - StratusGrid
Many AWS services automatically send logs or can easily be configured to deliver their logs to CloudWatch. Here is a list of services...
Read more >Going Beyond CloudWatch: 5 Steps to Better Log Analytics ...
CloudWatch is Amazon's primary monitoring and logging service built into the AWS cloud. It can collect logs and metrics from all AWS services ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
+1
This is a must have
Ok, got it. So it sounds like the background ones would be useful but, in the immediate sense, are more like a “nice to have” and the core ask right now is in your own usage of the logger. Does that sound correct?
For the initial implementation at least, I’m thinking it might be best to restrict it to that since having it be automatic for the background Amplify logging will require a lot more work to run through everything…plus it would require some extra thought regarding cloudwatch pricing and log storage.
Like I said, I’m investigating this now and having some discussions with the team on this issue. Don’t hesitate to comment with additional info.