CloudWatch task handler doesn't fall back to local logs when Amazon CloudWatch logs aren't found #27396
Description
This is really a CloudWatch handler issue - not "airflow" core.
Discussed in #27395
Originally posted by matthewblock October 24, 2022
Apache Airflow version
Other Airflow 2 version (please specify below)
What happened
We recently activated AWS Cloudwatch logs. We were hoping the logs server would gracefully handle task logs that previously existed but were not written to Cloudwatch, but when fetching the remote logs failed (expected), the logs server didn't fall back to local logs.
*** Reading remote log from Cloudwatch log_group: <our log group> log_stream: <our log stream>
What you think should happen instead
According to documentation Logging for Tasks, when fetching remote logs fails, the logs server should fall back to looking for local logs:
In the Airflow UI, remote logs take precedence over local logs when remote logging is enabled. If remote logs can not be found or accessed, local logs will be displayed.
This should be indicated by the message *** Falling back to local log.
If this is not the intended behavior, the documentation should be modified to reflect the intended behavior.
How to reproduce
- Run a test DAG without AWS CloudWatch logging configured
- Configure AWS CloudWatch remote logging and re-run a test DAG
Operating System
Debian buster-slim
Versions of Apache Airflow Providers
No response
Deployment
Official Apache Airflow Helm Chart
Deployment details
No response
Anything else
No response
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct