Airbyte log sweeping

Can’t seem to continue on this thread:

I would like to sweep Airbyte logs more frequently as our tables are quite big and hence the respective logs are also bigger than usual, causing disk space to become full.

Using the above link as a guide, I’ve added to the .env file:

I expect any logs older than a day to be cleared, but that doesn’t seem to happen.

I am using Docker and EC2 Linux 2 AMI and followed official Airbyte docs.

Is there an issue here or am I doing it wrong ?

Any help is appreciated.

I’ve tested this on 0.39.5-alpha and 0.40.8 on a t2 large instance with 50 Gb of storage

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.
The Community Assistance Team

Hello, unfortunately that config was removed with Scheduler.

The current solution (as of v0.40.5, so you will have to upgrade) is to clean up files from the workspace by default every 30 days:

This is configurable, so you should be able to set it to retain logs for only 1 day by setting the env TEMPORAL_HISTORY_RETENTION_IN_DAYS=1

Does this apply to logs on the minio as well?