potiuk commented on issue #25254: URL: https://github.com/apache/airflow/issues/25254#issuecomment-1194565953
> also... could consider just more regimented debug logging through normal logger, so that we could conceivably derive the state changes after the fact? Yep. This is precisely what OTel integration and especially Traces should provide. And they could provide it on much better lavel. For example - you will be able to trace way more than jusst task instance state changes - but also all the "deferred" behaviours in Triggerer. I think asking triggerer for example to save all the possible state changes to the meta-data DB is quite counter-productive, when you look at the usage patterns of Triggerrer - everything is asynchronous there except deferring/resuming a task. But with OTEL I think we could trace more events related to a particular task instance (and asynchronously, much more efficiently send it to remote telemetry service). Some Triggers might have multiple states between "defer" and "resume" - @howardyoo I think your comments might be cool too. -- 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]
