How to disable component file logging (scheduler, worker) and log only to stdout/stderr? #57535
Unanswered
bun-paul-kwon
asked this question in
Q&A
Replies: 1 comment
-
|
Hello, @potiuk Excuse me, I was wondering if you could provide some help. I'm trying to find out if it's possible to output all logs for If you have any information or guidance on this, I'd greatly appreciate it! 🙏 Thank you! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Airflow community,
We are currently using AWS MWAA (Celery Executor) and considering migrating to Airflow 3.0.2 on Kubernetes (AWS EKS).
Our task logs are configured to use remote logging to S3, and this is working well. Our configuration(
values.yaml) for this is:Our question is about the logs for Airflow components (e.g., scheduler, dag-processor, worker), not the task logs.
We've observed the following behavior in the Helm chart:
apiserverlogs only tostdout/stderr(which is our desired behavior).scheduler,dag-processorandworkerpods log to bothstdout/stderrAND local files (in/opt/airflow/logs).logGroomerSidecaris needed to clean up these local files.Our goal is to disable local file logging for all components (scheduler, worker, dag-processor) and have them log only to
stdout/stderr.We use Datadog autodiscovery, which scrapes these
stdout/stderrstreams for logging. The local file logs are redundant for us, and we would like to disable thelogGroomerSidecarcontainer entirely.Is there a recommended way to configure this using the Helm chart
values.yaml?Thank you for your guidance!
Beta Was this translation helpful? Give feedback.
All reactions