potiuk commented on issue #28647: URL: https://github.com/apache/airflow/issues/28647#issuecomment-1667762038
I think you are wrong @DFINITYManu. If you are using 2.6 (latest) version of Airlfow, There was a change implemented that logs from Triggerer https://github.com/apache/airflow/pull/27758 that enabled: 1) seeing triggerer logs in webserver 2) forwarding them to remote logging if you have remote logging configured If neither of that does not work for you, then likely you have something misconfigured, or maybe you are not using Airflow 2.6. Note, that you might underestimate complexity of the problem BTW. Logs raised in the trigger cannot be **JUST** written to a log file, because the trigger code is executed in a tight asyncio loop that should be executed as soon as possible and it cannot do any synchronous operations (including writing to a file or sending it over TCP). People who implement the solution I described went to a great extent to have a compleley custom implementation of storing the logs in memory and having completeley separate threads that are processing the logs and making them available either to the webserver or to remote logging handler that forward to to GCS/S3/ whatever can "properly" collect your logs. If you do not understand the complexity involved, and summarise it with one "properly" world, then I would like to ask you for a litle bit of empathy and appreciation of the work of people who do it in their free time to build the software that you can use for free, (and without any guarantees of any sort)., Because - in case you have not noticed - this is how Airflow is developed and you paid exactly 0 for the sofware you are using. A little more appreciation would go a long way. And if you want to be a good member of the community - if you still have problems after following the helpful advices (including using latest airflow and using remote logging), the `proper` thing to do will be to open an issue or discussion and describe your problem in detail.This is the best way you can help community to build a better software. Thank you for your understanding and I hope you will enjoy many years of using open source software for free (in the past and in the future). People who spend they nights and weekends on spending their personal time are counting on that. -- 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]
