potiuk commented on PR #39908: URL: https://github.com/apache/airflow/pull/39908#issuecomment-2252494154
I'd say with Airflow 3 work started - we should hold on with "fixing" it in Airflow 2 and simply follow whatever we decide on for Airflow 3. That needs someone to take a lead on driviing to consensus and agreeing our metrics/telemetry strategy for Airflow 3: 1) Are we going to stay with Statsd or OTEL only (I.e. is there something missing from OTEL that will make us stay with statsd) 2) If we are going to stay with statsd - should we align all the timers and "break" compatibility I think what @shubham22 mentioned at last dev call they are going to verify if that is something that they heavily would rely on and it will be discussed further at the dev calls. -- 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]
