Logging Errors
irarayjenkins opened this issue · comments
A client application can use a custom logger, and properly pass that into this library and then correctly observe the relevant logs. Since this library uses ampq-connection-manager to support connection resiliency, auto-reconnect, and message queueing... are these logs produced on disconnect actually errors?
I wonder if there is a way for a client application to configure this behavior to either avoid these logs completely and implement their own .on('disconnect', ... ) or to consider changing these to warnings or info/log?
One option of course, would be a custom logger just for this library that either consumes the logs or de-escalates error to a warn?