I believe the bug should be in "confirmed" state because we lose rabbitmq logs. If the right way to solve this issue is using logrotate instead of native rabbitmq logrotation please implement that.
I believe the bug should be in "confirmed" state because we lose rabbitmq logs. If the right way to solve this issue is using logrotate instead of native rabbitmq logrotation please implement that.