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

   ### Apache Airflow version
   
   2.9.3
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   I’ve recently migrated from StatsD to OpenTelemetry and am now sending 
metrics to Splunk Observability. 
   
   However, I’ve noticed that some metrics are now missing after this change, 
such as `operator_successes`, `operator_failures`, and some `custom metrics` 
that I used to see when using StatsD with the Python **stats**  package in my 
DAGs.
   
   
   The common factor among the missing metrics is that their descriptions in 
the [Airflow 
documentation](https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/logging-monitoring/metrics.html#metric-descriptions)
 mention **_“Metric with xyz tagging.”_** I’m not sure if this is relevant.
   
   ### What you think should happen instead?
   
    All metrics, including `operator_successes`, `operator_failures`, and 
`custom metrics`, should be available as they were with StatsD.
   
   ### How to reproduce
   
   
   - Migrate from StatsD to OpenTelemetry.
   - Send metrics to Splunk Observability.
   - Observe the missing metrics such as `operator_successes`, 
`operator_failures`, and `custom metrics`.
   
   ### Operating System
   
   Azure AKS linux 
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### 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