LSparkzwz opened a new issue, #43833:
URL: https://github.com/apache/airflow/issues/43833

   ### Apache Airflow version
   
   Other Airflow 2 version (please specify below)
   
   ### If "Other Airflow 2 version" selected, which one?
   
   v2.10.2
   
   ### What happened?
   
   We deployed Airflow in a Kubernetes cluster through Helm Chart 
(https://github.com/apache/airflow/tree/main/chart) with statds enabled, the 
configuration for statsd is the default one.
   
   The issue involves being able to see most metrics except for 
dagrun.duration.success.<dag_id> and dagrun.duration.failed.<dag_id>
   
   ### What you think should happen instead?
   
   The metrics dagrun.duration.success.<dag_id> and 
dagrun.duration.failed.<dag_id> should be visible in the exporter
   
   ### How to reproduce
   
   1.     Deploy Airflow on Kubernetes with the official helm chart
   2.     Set up Statsd exporter for metric collection
   2.     Schedule sample dag runs to generate metrics
   3.     dagrun.duration.success.<dag_id> and dagrun.duration.failed.<dag_id> 
metrics will be not be available on the statds /metrics path
   
   ### Operating System
   
   Oracle Linux 9
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   In this issue https://github.com/apache/airflow/issues/18630 you suggest to 
deploy a custom Airflow image in order to enable TCPStatsClient but I am unable 
to do that, is there any way to do such thing through helm chart values?
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to