How to log when building custom destination connector

Platform, Deploy & Infra Issues
, ,
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: MacOS… are some example remove it with yours
  • Deployment: Kubernetes
  • Airbyte Version: 0.40.26
  • Source name/version:
  • Destination name/version: custom destination connector
  • Step: The issue is happening during sync
  • Description: I built a custom destination connector and I wanted to add some logging into it. I used print to output the state of the sync process onto the airbyte UI. It works fine when I had airbyte version 0.40.15 but I recently updated Airbyte to 0.40.26 and I am not able to see any of the print statement anymore.
    I have tried adding logging with the python logging module that did not work. I am reading from a snowflake table and writing to some API. I basically want to see the response while writing to the API. What am i doing wrong?
2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

3

Heyy there ! If using stream (extending Stream), you have access to logger as a property of your stream connector, and thus you can do self.logger to access the logger (info / warn / error…)