Aaron Silverman
10/26/2023, 1:13 AMkapa.ai
10/26/2023, 1:14 AMLOG_CONNECTOR_MESSAGES=true in your local airbyte-platform repository. This will log the messages the Airbyte platform receives from the source and destination when debugging locally. For example, you can use the command LOG_CONNECTOR_MESSAGES=true VERSION=dev docker compose up to start the platform with logging enabled. [source](https://docs.airbyte.com/contributing-to-airbyte/resources/developing-locally) For your custom destination connector, all logging should be done through the self.logger object available in the Destination class. If you log outside of this object, the logs will not be shown properly in the Airbyte UI. [source](https://docs.airbyte.com/connector-development/tutorials/building-a-python-destination) In the write method of your destination connector, you should be implementing the logic to write data to the underlying destination. This method reads a configuration, a stream of records from stdin, and a configured catalog describing the schema of the data and how it should be written to the destination. You can add logging statements within this method using the self.logger object to track the progress of the data writing process. [source](https://docs.airbyte.com/connector-development/tutorials/building-a-python-destination) Here is an example of how you might use the logger in the write method: python def write(self, config, configured_catalog, input_messages): # Your implementation here <http://self.logger.info|self.logger.info>("Writing data to destination...") # More implementation <http://self.logger.info|self.logger.info>("Data written successfully.") Please note that the above code is a simplified example and your actual implementation may vary.Aaron Silverman
10/26/2023, 1:19 AM