You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Monolog FallbackGroupHandler expects handlers to throw error while they are handling the records. CloudWatch handler does not throw cloudwatch connection related errors during call to handling process.
Only when everything is finished (in close()), CloudWatch handler realizes that its not able to connect etc. and then there is an exception, but it's already too late in case of FallbackGroupHandler.
Expected behavior
CloudWatch should check during the handling of the record, if it's able to connect to cloudwatch service or not. If it's not able to connect, it should through proper error.
Please provide the steps to reproduce and if possible a minimal demo of the problem
Define a FallbackGroupHandler with CloudWatch as first handler and file as second handler in the group.
Make cloudwatch service fail (wrong credentials etc.)
Expected: File handler is executed when CloudWatch handler fails.
Actual: File handler is not executed when CloudWatch handler fails, because CloudWatch handler does not throw exception during handle() call.
Please tell about your environment:
PHP Version: 7.3.12
Operating system (distro): Alpine Linux v3.10
Application mode:
Web app
CLI app
The text was updated successfully, but these errors were encountered:
Describe the bug
Monolog FallbackGroupHandler expects handlers to throw error while they are handling the records. CloudWatch handler does not throw cloudwatch connection related errors during call to handling process.
Only when everything is finished (in close()), CloudWatch handler realizes that its not able to connect etc. and then there is an exception, but it's already too late in case of FallbackGroupHandler.
Expected behavior
CloudWatch should check during the handling of the record, if it's able to connect to cloudwatch service or not. If it's not able to connect, it should through proper error.
Please provide the steps to reproduce and if possible a minimal demo of the problem
Please tell about your environment:
The text was updated successfully, but these errors were encountered: