jordi-crespo commented on issue #35817: URL: https://github.com/apache/airflow/issues/35817#issuecomment-1825630340
> Reading this I can confirm that statsd is working in our setup in K8s with the standard helm chart very stable sine ~1 year at least. Am I correct to assume that your statsd container is _not_ deployed via the helm chart but you use helm just for the airflow deployment itself and point to an external statsd (hosted separately)? Are you sure it is good to use a base IPv4 address and not a host name? Correct to assume your statsd is outside of K8s and the IP is stable and reachable (no firewall)? From the screenshot I see that you missed to set the statsd reporting to "on"? Can you double check your config as described in https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#statsd-on ? It is disabled per default if not explicitly set. According to the links to datadog and airflow, they say to use the environmental variables in this way in the containers: https://docs.datadoghq.com/integrations/airflow/?tab=containerized#connect-airflow-to-dogstatsd and https://airflow.apache.org/docs/helm-chart/1.9.0/production-guide.html The environmental variable statsd on was set to false, because if I set it to true I get the following error: ``` ERROR - Unexpected error: encoding with 'idna' codec failed (UnicodeError: label empty or too long) ``` It is a host IP because according to the links I sent you, it says to use the IP of the node where airflow is running. I have checked that this works, so I guess the problem must be in airflow, but I don't understand where the problem lies. I see that there is the possibility of creating a container for statsd, but I don't see how I could configure it to use it with datadog, since from what I understand in the guides, it has to be used using the env variables. What do you think about this after I have given you more context? -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
