Skip to content

Describe_log_streams and filter_log_events calls breaks put_log_events

0

We have applications that send a fairly large amount of logs into cloudwatch logs.

Yesterday, someone was attempting to filter those logs, running potentially many describe_log_streams and filter_log_events call for a fairly small time window but for a time a month in the past. (time window of 20 minutes or less)

All of a sudden, the code that issues put_log_events calls started getting the following errors.

400 Bad Request, ResourceNotFoundException The specified log stream does not exist

It seems the filter and describe_log_streams requests broke the ability to send additional logs.

How careful do we need to be when issuing these types of requests?

asked 8 years ago537 views

1 Answer
1

This was user error. The error message was accurate. The log stream had been deleted.

answered 8 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.