ianbuss opened a new issue, #50963: URL: https://github.com/apache/airflow/issues/50963
### Description Currently, there is a single `enable_pretty_log` boolean option in the [configure_logging](https://github.com/apache/airflow/blob/fb8c8770b3ff8cdab84df18ea61dbf639e55fc86/task-sdk/src/airflow/sdk/log.py#L249) method, which defaults to `True`. If `True` it means structlog will: * Use colorised output * Add `rich` traces to exceptions * Use `"%Y-%m-%d %H:%M:%S.%f"` timestamps * Use console logger If `False` it means: * Use json logger * Use iso format timestamps * Use structlog's dict exception renderer For users who would like a console logger but no colorised output and no rich traces this is not possible right now. Moreover, Celery defaults to `enable_pretty_log = True`, which makes the logs somewhat difficult to read in log ingestion solutions like Splunk, where the color escape sequences are rendered as raw text. ### Use case/motivation Have the option to have plain text, non-colorised console logger output via the existing https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#colored-console-log config parameter and have that be respected by the executors. ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
