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
The message is not added in the log so when we look at logs. We can't see which message with which data have failed.
The idea is to add the message content to debug easily.
Example
No response
The text was updated successfully, but these errors were encountered:
I usually store in database the failed message prior to retry, so you end up seeing all data (with the failed transport configured with doctrine)
but here for your issue in raw logs, perhaps adding a logger->debug($message) with the data can be useful indeed, and after let monolog config handle the case that debug log are streamed or not (to not flood logs if unwanted)
or as well mimicking what the workflow component has, a listener to audit that can be activated if needed
Description
Currently, when using
symfony/messenger
, we can not see the message which failed in the logs.When looking at this :
https://github.com/symfony/symfony/blob/7.3/src/Symfony/Component/Messenger/EventListener/SendFailedMessageToFailureTransportListener.php#L61
Or this :
https://github.com/symfony/symfony/blob/7.3/src/Symfony/Component/Messenger/EventListener/SendFailedMessageForRetryListener.php#L73
The message is not added in the log so when we look at logs. We can't see which message with which data have failed.
The idea is to add the message content to debug easily.
Example
No response
The text was updated successfully, but these errors were encountered: