Disabling colors in the logs

achooin · July 13, 2025, 8:52am

I feed all the my Docker logs into an observability pipeline.

Unfortunately the ANSI color escape sequences mess with the parsing.
For example,

│2025-07-13T08:21:39.587007Z  INFO sqlx::postgres::notice: relation "_sqlx_migrations" already exists, skipping         │

comes out looking like:

[2m2025-07-13T08:21:39.587007Ze[0m e[32m INFOe[0m e[2msqlx::postgres::noticee[0me[2m:e[0m relation "_sqlx_migrations" already exists, skipping

making it difficult to parse.

Looking at Docker | Atuin Docs, I saw the envvar RUST_LOG mentioned and that gave me hope that RUST_LOG_STYLE: "never" would work out of the box, but that didn’t work.

Confusingly, I saw PR #642 talking about ATUIN_LOG replacing RUST_LOG? (Sorry I’m only allowed to include 2 links in this post)

Is there a way to disable colors for log output?

ellie · July 14, 2025, 3:40pm

We try to follow https://no-color.org/

So if you set NO_COLOR=true, it should do what you want!

We switched to ATUIN_LOG because people working on Rust projects + using Atuin found that they conflicted + got output they didn’t want

achooin · July 14, 2025, 4:35pm

So are you saying that the RUST_LOG mentioned here needs to be updated in the docs?

github.com/atuinsh/docs

src/content/docs/self-hosting/docker.mdx?plain=1

9b207d5b2


      
              volumes:
                - "./config:/config"
              links:
                - postgresql:db
              ports:
                - 8888:8888
              environment:
                ATUIN_HOST: "0.0.0.0"
                ATUIN_OPEN_REGISTRATION: "true"
                ATUIN_DB_URI: postgres://$ATUIN_DB_USERNAME:$ATUIN_DB_PASSWORD@db/$ATUIN_DB_NAME
                RUST_LOG: info,atuin_server=debug
            db:
              image: postgres:14
              restart: unless-stopped
              volumes: # Don't remove permanent storage for index database files!
                - "./database:/var/lib/postgresql/data/"
              environment:
                POSTGRES_USER: ${ATUIN_DB_USERNAME}
                POSTGRES_PASSWORD: ${ATUIN_DB_PASSWORD}
                POSTGRES_DB: ${ATUIN_DB_NAME}
          ```

ellie · July 14, 2025, 4:46pm

No, it works as expected for the server. ATUIN_LOG is for the client