Support for Clean Logs in Windmill Docker Containers with AWS CloudWatch

[andreasotto]

Hello Windmill team,

We are currently evaluating Windmill in a self-hosted setup using Docker containers. Our logging system relies on AWS CloudWatch, which we configure in the docker-compose.yml file with driver: awslogs.

Unfortunately, we’ve encountered an issue with the resulting logs: they contain ANSI color codes that seem suited only for local terminal environments. This makes the logs more then difficult to read and parse in a professional setup like AWS CloudWatch, where clean, structured logs are essential.

Example of the problematic logs:

�[2m2024-11-20T22:32:12.668393Z�[0m �[32m INFO�[0m �[1mworker�[0m: �[2mwindmill-worker/src/worker.rs�[0m�[2m:�[0m�[2m1133�[0m�[2m:�[0m ping update, memory: container=23MB, windmill=13MB �[2m�[3mworker�[0m�[2m=�[0mwk-default-b78f098beb95-R78CG �[3mhostname�[0m�[2m=�[0mb78f098beb95�[0m

We’ve tried setting environment variables like NO_COLOR=1 and TERM=dumb for the containers, but this hasn’t resolved the issue.

Question:
What is the recommended way to configure Windmill containers so that they produce clean logs without unnecessary ANSI color codes?

We appreciate your guidance on this matter. Thank you!

[rubenfiszel]

hello,

Use JSON_FMT=true to have json formatted logs