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
There are many ways to solve this, I do see that I can pass in my own logger but it's an all or nothing in this module with no way to decipher as a consumer if a message is error or not. The Creating a pool connected to [server] message should not be logged as an error
The alternative is that everything is silent and instead it would be nice if actual errors get logged and info messages (connection pool created) getting logged as something else. Something that can take in a more intelligent logger with different log levels being implemented in this module.
The text was updated successfully, but these errors were encountered:
If you log successful connections to STDOUT, and disconnections to STDERR, then you need to look at both logs to know the state of your pool (connected or not). If they are dumped in two different files, this is a pain to do.
There are many ways to solve this, I do see that I can pass in my own logger but it's an all or nothing in this module with no way to decipher as a consumer if a message is error or not. The
Creating a pool connected to [server]
message should not be logged as an errorThe alternative is that everything is silent and instead it would be nice if actual errors get logged and info messages (connection pool created) getting logged as something else. Something that can take in a more intelligent logger with different log levels being implemented in this module.
The text was updated successfully, but these errors were encountered: