[BUG] Not able to disable logs

Feedback
1

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

Self-hosted

If you are self-hosting, what version of Baserow are you running?

version 1.33.1

If you are self-hosting, which installation method do you use to run Baserow?

using docker compose

What are the exact steps to reproduce this issue?

  1. set env variables to:
    BASEROW_ENTERPRISE_AUDIT_LOG_RETENTION_DAYS=0
    BASEROW_BACKEND_LOG_LEVEL=ERROR
    BASEROW_CELERY_BEAT_DEBUG_LEVEL=ERROR
    BASEROW_BACKEND_DATABASE_LOG_LEVEL=ERROR

  2. restart container by docker compose up -d

  3. run docker logs baserow → logs are still visible (new)

Even though I have set these env variables, the logs are still there, I have verified that my env variables are loaded in the container

2

Hey @yashkumar can you give some more details what do you want to achieve?
Do you want to disable logging for baserow application, do you want to completely disable docker logs or both?

You have mentioned that after setting those variables and restarting you still see new logs on console but are they stored anywhere?

3

I don’t want baserow to write logs, even though I have set it to ERROR only, it still writes INFO logs

I guess they are stored in the enterprise logs table, I have set the retention days to 0 but the tables is still created after dropping it manually.

4

Setting BASEROW_ENTERPRISE_AUDIT_LOG_RETENTION_DAYS=0 only affects retention, not creation.
In this case your logs will be “expired” next time clean_up_audit_log_entries celery task is run those records will be removed.

You can control how often cleanup task is called with BASEROW_ENTERPRISE_AUDIT_LOG_CLEANUP_INTERVAL_MINUTES which by default is 24h

I.e. if you set it to 1h, then you will have audit logs cleaned every hour (but you will still have new info entries there for 1h).

Other variables do not affect audit log.