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

   ### Apache Airflow version
   
   main (development)
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   with `AIRFLOW__METRICS__METRICS_USE_PATTERN_MATCH` set to `true` and 
`AIRFLOW__METRICS__METRICS_ALLOW_LIST` set to `.*get_astronauts.*` , I notice 
several other metrics being sent to datadog that don't match the pattern:
   
![image](https://github.com/apache/airflow/assets/20266953/16510682-9e45-48c1-9a95-ce726996cca5)
   
   
   ### What you think should happen instead?
   
   Following metrics shouldn't be showing up on datadog when the allow list is 
`.*get_astronauts.*`:
   
   1. `airflow.dag.task.duration.*`
   2. `airflow.ti.*`
   3. `datadog.*` (Not sure if we have any control to block these)
   
   ### How to reproduce
   
   env variables:
   
   AIRFLOW__METRICS__STATSD_DATADOG_ENABLED | true
   -- | -- 
   AIRFLOW__METRICS__STATSD_DATADOG_TAGS | testNo:C2
   DATADOG_API_KEY | ● ● ● ● ● ● ●
   AIRFLOW__METRICS__METRICS_USE_PATTERN_MATCH | true
   AIRFLOW__METRICS__METRICS_ALLOW_LIST | `.*print_astronaut_craft.*`
   
   
   Once you update your datadog key here, you will start seeing metrics in 
datadog-->metrics-->summary . use the tag `testNo:C2` to filter
   
   ### Operating System
   
   Debian GNU/Linux 11 (bullseye)
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Astronomer
   
   ### 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