Use standard logger with custom handler in python integrations

[eugene-kulak]

Tell us about the problem you're trying to solve

Currently, we are using AirbyteLogger

• a custom logger. The problem is that even though it looks like standard one, it behaves differently and lacks some features, the following would not work:

logger.info("Message: %s, code: %d", message, code")

Other features like enable/disabled some levels, duplicate messages to other sources (files, network, monitoring) adding custom formatters and user context, all this would not work as well.

Describe the solution you’d like

Use the standard logger class.

Describe the alternative you’ve considered or used

Implement custom Handler instead (or Formatter) and attach it to a specific logger (by name or explicitly in the code).

class AirbyteLogFormatter(logging.Formatter):
    def format(record)
        message = super().format(record)
        log_message = AirbyteMessage(type="LOG", log=AirbyteLogMessage(level=record.level, message=message))
        return log_message.json(exclude_unset=True)

logger = logging.getLogger('airbyte.source.zabbix')
logger.setLevel(logging.DEBUG)
handler = logging.StreamHandler(stream=sys.stdout)
handler.setFormatter(AirbyteLogFormatter())
logger.addHandler(handler)

Additional context

Add any other context or screenshots about the feature request here.

┆Issue is synchronized with this Asana task by Unito

[cgardens]

@ChristopheDuong - is this something you'd be familiar with? if it is we might tackle it in the next few weeks.

[cgardens]

@sherifnada assigning to you as a "connector stability" task. Up to you to decide if this is something we should do now or not.