uranusjr opened a new pull request, #42301: URL: https://github.com/apache/airflow/pull/42301
Airflow does not currently have any logging for listeners, and only rely on individual listeners to log responsibly. This causes issues when a listener does not do it since it would have no trace at all in logs, and it is extremely difficult to find exactly what the offending component is (especially we would not even know a listener is at fault). This uses pluggy's hok monitoring feature to add logs when Airflow is calling a hook, and when a hook finishes executing. This should allow us to more easily identify when a hook emits an unhandled exception (it'd trigger the 'before' logging but not 'after'), and also provide some context what's passed into the hook for debugging. Ref: https://pluggy.readthedocs.io/en/stable/#call-monitoring I also referenced how Datasette does this: https://github.com/simonw/datasette/commit/232a30459babebece653795d136fb6516444ecf0 -- 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]
