Bowrna commented on issue #33426:
URL: https://github.com/apache/airflow/issues/33426#issuecomment-1805099545
sure @potiuk Please let me know if you need any details from me on this
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Git
potiuk commented on issue #33426:
URL: https://github.com/apache/airflow/issues/33426#issuecomment-1807198703
Yeah. Start with the docs. I think we might want to do more of a consistency
push when we add traces and then we can clean it up and make some consistent
approach.
--
This is an
Bowrna commented on issue #33426:
URL: https://github.com/apache/airflow/issues/33426#issuecomment-1844869635
hi @potiuk did you get a chance to analyze this part in detail? I will push
changes in doc saying it is milliseconds info that statsd client pushes
--
This is an automated message
potiuk commented on issue #33426:
URL: https://github.com/apache/airflow/issues/33426#issuecomment-1849008476
Go ahead.
--
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 u
potiuk closed issue #33426: Statsd metrics dagrun.schedule_delay sends time in
different format against the seconds specified in docs
URL: https://github.com/apache/airflow/issues/33426
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Gi
Bowrna commented on issue #33426:
URL: https://github.com/apache/airflow/issues/33426#issuecomment-1790610192
This is the code I retrieved from the python StatsdClient and it shows that
timer if we pass the timedelta converts it into milliseconds and push it.
With that said could I s
potiuk commented on issue #33426:
URL: https://github.com/apache/airflow/issues/33426#issuecomment-1798600877
I am good for it - but I would have to analyze it in detail to be sure :)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to G
