potiuk commented on issue #43432: URL: https://github.com/apache/airflow/issues/43432#issuecomment-2441282413
I think, it's the nature of statsd and we cannot do much about it (but I am not 100% sure) - and we are moving away from statsd in favour of open-telemetry https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/logging-monitoring/metrics.html#setup-opentelemetry. While we are not removing statsd, it's very likely we are not going to invest any time into improving or even fixing statsd problems. Mybe you could switch to using open-telemetry and see if you have similar problem there - this is anyhow "future" of airflow telemetry - and it has way better features than statsd (including support for open-telemetry traces in 2.10.*) - so the best course of action would be to try it out @eanikindfi - otherwise you might hope that some will look at this one, but it's unlikely statsd will get a lot of love from the side of maintainers. cc: @howardyoo @ferruzzi -- 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]
