shayoo9814 opened a new issue, #37078:
URL: https://github.com/apache/airflow/issues/37078
### Description
Today, Airflow users lack the ability to configure Airflow Webserver logs.
(Users can only configure [access
logs](https://docs.gunicorn.org/en/stable/settings.html#accesslog),
boring-cyborg[bot] commented on issue #37078:
URL: https://github.com/apache/airflow/issues/37078#issuecomment-1915763537
Thanks for opening your first issue here! Be sure to follow the issue
template! If you are willing to raise PR to address this issue please do so, no
need to wait for ap
potiuk commented on issue #37078:
URL: https://github.com/apache/airflow/issues/37078#issuecomment-1915819055
You can configure gunicorn settings by GUNICORN_CMD_ARGS variable
https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/logging-monitoring/loggin
potiuk closed issue #37078: Add two new fields (gunicorn_logconfig &
gunicorn_logconfig_dict) to airflow.cfg to allow users to configure Airflow
Webserver logs
URL: https://github.com/apache/airflow/issues/37078
--
This is an automated message from the Apache Git Service.
To respond to the m
shayoo9814 commented on issue #37078:
URL: https://github.com/apache/airflow/issues/37078#issuecomment-1915906602
I still believe there is value to be gained from the proposed change for the
following reasons.
1. Consistent interface for Airflow customizations
`airflow.cfg` is what us
potiuk commented on issue #37078:
URL: https://github.com/apache/airflow/issues/37078#issuecomment-1916382058
No. This is wrong assessment.
We already have few 100s of options in airflow config and we do not want to
bloat it with even more stuff. Airflow config is actually one of the
