I’m running a local instance of airbyte, and I’m a...
# replication-troubleshooting
a
I’m running a local instance of airbyte, and I’m attempting to use a timestamp filter within my request parameter for an incremental build. My airbyte syncs are returning no records with the latest start time produced by the latest record, but records are returned when I attempt the request with the same timestamp in postman. The requests for the source aren’t produced in the logs. Which container should I begin to explore to find the API request made during a sync?
s
The sync logs are easiest found in the airbyte UI. Airbyte uses worker containers to run jobs that interact with connectors: https://docs.airbyte.com/understanding-airbyte/jobs/ You'll find logs in there, but my understanding is that it can be annoying to piece everything together so it might be best through the UI 😛 If you can share the sync log here, I'll help dissect it
Hey @Adham Suliman thanks for sharing the additional context! I have some ideas that might help. You can set debug logging by setting the environment variable
LOG_LEVEL=DEBUG
as per the boilerplate .env in the repo. If deploying with docker, you should be able to run
LOG_LEVEL=DEBUG docker compose up
to get the logs you need. If they are still not giving enough info, there's some logging configuration that might help: https://docs.airbyte.com/contributing-to-airbyte/developing-locally#inspecting-the-messages-passed-between-connectors Let me know if this helps or if I can look into anything else! Good luck.