-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handling large amounts of CloudWatch Logs in toHaveLog() #29
Comments
@abbyhuisman-rw thanks for opening this issue. |
@abbyhuisman-rw I've looked at the library's code and I'm already limiting the results to 1 so I'm not sure I'll get into the pagination issue. Please let me know if it makes sense to you too :) |
@erezrokah Thanks for making that change. Our internal change looks almost exactly like your code so I think this PR will allow us to remove our home-grown solution. I didn't notice the limit one so hopefully that in tandem with the start time will fix our issue. Any idea when you will do a formal release of this code? |
Thanks that’s great. I’m AFK, but I’ll do a formal release tomorrow and update (and close the issue) once I do. |
@abbyhuisman-rw Formal release |
Note: |
Is your feature request related to a problem? Please describe.
We've been noticing our tests fail as the CloudWatch log streams grow and it is largely due to the AWS SDK returning multiple pages of CloudWatch Logs.
Describe the solution you'd like
At RobustWealth, we've added a wrapper around the SDK to page the logs along with giving a start and end date to retrieve a smaller subset of logs. Instead of rolling our own solution we would like to add this feature into this library and we'd be willing to contribute back our solution.
Describe alternatives you've considered
We've considered deleting our logs, this fixed our issues but then we lose the information we need to properly monitor our applications.
The text was updated successfully, but these errors were encountered: