potiuk commented on PR #22588:
URL: https://github.com/apache/airflow/pull/22588#issuecomment-1129061369
> We can still have a flag on the `scheduler` and `webserver` commands,
`--display-conf-at-startup/--do-display-conf-at-startup` (mouthful name I know
-- but that's an example) that allows controlling the behaviour as there are
many who would not want to see the those conf at starttup.
The problem is that those who need it (and come to use with issues), have
usually no good idea nor control on how to change their systemd or similar
configuration. Asking those people to modify their deployment configuration to
add their options when they have really vague idea how their airflow is started
in teh first place is pretty counter-productive. The idea is to get good
answers on what configuration is used - without them having to understand that
first.
I think (as long as we do it once at startup) - there is literally 0
overhead to print configuration (especially the non-default one) to the logs.
We are really talking about the case where:
a) there is an "admin" of airflow who vaguely knows how their system is
configured (happens when you have a new person which is tasked with Airflow
maintenance)
b) that persons sees a strange behaviour and is not able to diagnose it so
it runs cli to send and it shows some configuration which is reported to us
("yes I have it configured this way").
I simply want to have a way to tell the user "are you 100% sure this is what
your webserver does" - can you open your logs and show the "startup" logs of
the webserver?
In many cases showing the logs will be far easier to ask the user for rather
than "check whatever configuration your deployment starts airflow with" -
because then we might not get authoritative answer, we might guess ourselves
and the admin might guess it too without knowing exactly the systemd
configuration. Been there, done that many times.
Yeah. Those poople **should** no better. But by seing the configuration we
can actually tell them that because we will see what they think about their
configuration is wrong - before that we can just guess it, and we might guess
wrongly.
--
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]
