howardyoo commented on issue #37628: URL: https://github.com/apache/airflow/issues/37628#issuecomment-3602337374
I'm not actively working on the otel logs support, nor have plans to do it right now. Like Jarek mentioned, it may involve more than the effort of implementing metrics and traces, as the way Airflow is logging things are quite complicated. I do believe that many users might be interested in sending 'task logs' via OTEL protocol, and in that case, developing and contributing as a logging handler that is compatible with OTEL might be a way, rather than implementing it as Airflow's native logging. On Mon, Dec 1, 2025 at 6:59 PM Jarek Potiuk ***@***.***> wrote: > *potiuk* left a comment (apache/airflow#37628) > <https://github.com/apache/airflow/issues/37628#issuecomment-3599637535> > > @chris-stetter <https://github.com/chris-stetter> "plans" might be a > strong word. It's been mentioned as a "some day" feature, but I don't > believe anyone is actively working on that feature at the moment. > > Well. Anyone can try (including you @chris-stetter > <https://github.com/chris-stetter> ) - however so far also our assesment > was that logging integration in OTEL is quite a different beast. Not only > it is using quite a different approach than metrics and traces, but also it > would haevily interact with the way we are doing logging in Airflow. > Currently we are using structlogs and we also need integration of logging > at the level of Airlfow UI - where we have to display the logs from tasks - > not only from workers, but also from corresponding triggers - also it has > all the performance improvements when scrolling the logs where we have to > retrieve the logs only partially and K-Merge them when they are coming from > different sources for the same task. > > That makes the OTEL integration for logging far more risky and complicated > - so there is currently no active work on that and unless someone has a > very, very good reason to get it and invest time in it, it's unlikey to > happen "like that". > > But - implementing it yourself and testing or even finding someone who can > implement and your company will pay for is a good way to speed it up (or > even to implement it at all). > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/airflow/issues/37628#issuecomment-3599637535>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AHZNLLW5PBQ4XANE2JKGQUD37TP7ZAVCNFSM6AAAAACNWBMFDSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKOJZGYZTONJTGU> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- 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]
