lazywithclass/winston-cloudwatch

Messages permanently retry when the log group doesn't exist

Opened this issue · 1 comments

When the ensureLogGroup option is falsy, attempting to log a message causes it to be retried indefinitely.

For example, I set up an error handler that logs to the console. After attempting to log only one message, the handler outputs this until I either stop the transport or kill the process:

ResourceNotFoundException: The specified log group does not exist

This might be fixed by #184