potiuk commented on issue #30991: URL: https://github.com/apache/airflow/issues/30991#issuecomment-1531516415
> I fully understand. But we don't have any extra info that I can share. If I would I would share it. Airflow does not seem to be very verbose on this. I'll see if we can find a way to fix this, but it would probably mean moving away from GCS for remote logging. We consider it broken. Pity. You could have helped others with similar issues, I consider it's not broken, but badly configured but it's hard to say without your help. And while possibly airflow could be more verbose, it's also hard to say without knowing what the issue is, generally the user is responsible for putting airflow and monitoring it, people here are just volunteers, working on airflow for free so that users could use it for free and this often means that users need to invest into their deployments into making sure that the software that deploy run smoothly. I guess price to pay to use software that you use for free (also known as "there is no free lunch". This is also a reson why there are managed versions of Airflow where you pay others for doing it (making sure things run smoothly and **just work**). But on the I do agree GCS is not the best logging interface out there, there are other better (Stackdriver for example). -- 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]
