Owen-CH-Leung opened a new issue, #53526:
URL: https://github.com/apache/airflow/issues/53526

   ### Apache Airflow Provider(s)
   
   elasticsearch
   
   ### Versions of Apache Airflow Providers
   
   Airflow 3
   
   
   
   ### Apache Airflow version
   
   3
   
   ### Operating System
   
   Debian GNU/Linux 12 (bookworm)
   
   ### Deployment
   
   Docker-Compose
   
   ### Deployment details
   
   I use breeze to start an airflow 
   
   `breeze start-airflow --executor CeleryExecutor --backend postgres 
--load-example-dags --db-reset`
   
   ### What happened
   
   In Airflow 3, the api-server renders well-formatted task logs that allows 
filtering based on log level. For example, the following is the rendered task 
logs when using `FileTaskHandler` (disabling remote logging)
   
   <img width="1361" height="509" alt="Image" 
src="https://github.com/user-attachments/assets/fa082490-b829-435f-ac10-c24097c01bfc";
 />
   
   
   However, when using `ElasticsearchTaskHandler` (And 
`OpensearchTaskHandler`), the logs are not rendered nicely: 
   
   <img width="1153" height="500" alt="Image" 
src="https://github.com/user-attachments/assets/2ddde37f-3e0a-47ac-9afb-b06d0ef5a280";
 />
   
   ### What you think should happen instead
   
   `ElasticsearchTaskHandler` or `OpensearchTaskHandler` should render the task 
log nicely, just like `FileTaskHandler`
   
   ### How to reproduce
   
   Run `breeze start-airflow --executor CeleryExecutor --backend postgres 
--load-example-dags --db-reset` to start a local airflow. Trigger any of the 
DAG run. Ship the task logs to ElasticSearch / Opensearch. Then try to read 
task log from the webUI
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] 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]

Reply via email to