EMT-Swaroop opened a new issue, #39522:
URL: https://github.com/apache/airflow/issues/39522

   ### Apache Airflow version
   
   2.9.1
   
   ### If "Other Airflow 2 version" selected, which one?
   
   2.9.0
   
   ### What happened?
   
   According to airflow documentation, from 2.8.2 airflow version the metrics 
ti_failures, ti_successes, zombie_killed metrics need to have tagging task_id 
and dag_id
   
![image](https://github.com/apache/airflow/assets/105901854/e79a2287-4edb-477f-9a24-513e8bcceae3)
   
   Airflow 
documentation:https://airflow.apache.org/docs/apache-airflow/2.9.1/administration-and-deployment/logging-monitoring/metrics.html
   
   In our airflow environment we have upgraded airflow 2.9.1 and helm chart 
1.13.1. Still we are not able to see the tagging for setting up alerts and 
monitoring at task level.
   
   ### What you think should happen instead?
   
   The tagging of task-id and dag_id for metrics like ti_failures, 
ti_successes, zombie_killed need to be available so that we can locate the 
tasks accordingly to debug and we can have the alerting according to that.
   
   ### How to reproduce
   
   If we use 2.8.1 or later version tagging need to be there for mentioned 
metrics. But those are not coming, only the counter values are getting produced 
by the airflow statsd.
   
   ### Operating System
   
   Debian Bullseye
   
   ### Versions of Apache Airflow Providers
   
   recently we have upgraded to 2.9.1.
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] 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