ankane/pgsync

All Logs are Going to Stderr (contd)

ofiliojo opened this issue · 1 comments

The original issue #197 is closed, so I'm responding here:

Hey @ankane, thanks so much for the quick response. Please allow me to more clearly articulate my problem statement.

Most third-party log management systems make determinations as to the severity of the logs based on the standard stream definitions (i.e. STDERR is treated more severely than STDOUT). This leads to a much greater debugging difficulty when there are issues. Typically, users expect there to be some amount of tiering of service output, where errors that require the user to take action are separated from logs used to inform the user of expected runtime behavior.

The Logger in Ruby’s STL allows us to specify multiple loggers going to STDERR and STDOUT, in addition to including six of the eight standard linux log severity levels. I understand that it is quite a lift for pgsync, but the community as a whole would benefit from this because it would eliminate the need for any bespoke code to provide custom filters integration with standard log management solutions.

Again, I would be more than happy to submit this PR if you would be amenable to it.

Hi @ofiliojo, thanks for the additional context, but it's not something I'd like to change / support (however, you can always fork as needed).