Based on the information provided in the knowledge sources, it appears that you're experiencing an issue with excessive logging in Airbyte. While I don't have specific information about your exact error message, I can provide some relevant insights and suggestions: 1. Debug Logs: For non-testing environments, especially when running at-scale syncs, it's recommended to turn off DEBUG logs. Failing to do so can overload the server pod and disrupt normal operations. As mentioned in the [Airbyte documentation](https://docs.airbyte.com/enterprise-setup/scaling-airbyte#debug-logs): > We recommend turning off

DEBUG

logs for any non-testing use of Self-Managed Airbyte. Failing to do while running at-scale syncs may result in the

server

pod being overloaded, preventing most of the deployment for operating as normal. 2. Logging Level for JDBC Sources: There's an ongoing issue related to excessive logging in SQL integrations (MySQL, Postgres, BigQuery, etc.). A proposal has been made to change the logging level from INFO to DEBUG for these sources to reduce the number of log entries. This is discussed in a [GitHub issue](https://github.com/airbytehq/airbyte/issues/24983). 3. API Rate Limiting: If you're making a large number of API calls, you might be hitting rate limits. This could potentially cause errors and increased logging. As mentioned in one of the issues, a user experienced problems when triggering around 200 syncs/second through the Airbyte API [GitHub issue](https://github.com/airbytehq/airbyte/issues/44833). To address your specific situation: 1. Verify that DEBUG logs are indeed turned off, as you mentioned setting the logging level to error. 2. Check if you're using any JDBC sources, as these might be contributing to the log flood. 3. Review your API usage and consider implementing rate limiting or spreading out your sync job requests if you're triggering many syncs in a short period. 4. If the problem persists, you might want to consider opening a new issue on the Airbyte GitHub repository or reaching out to their support team with your specific error messages and configuration details. Remember, while these suggestions are based on similar issues reported by other users, your specific situation might require a more tailored solution. If the problem continues, it would be best to engage directly with Airbyte support or the community for more targeted assistance.