syun64 opened a new pull request, #29881:
URL: https://github.com/apache/airflow/pull/29881

   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of an existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   closes: #29663
   ---
   
   This PR adds two additional configuration parameters:
   ```
   statsd_disabled_tags:
         description: |
           If you want to avoid sending all the available metrics tags to 
StatsD,
           you can configure a blocklist of prefixes (comma separated) to 
filter out metric tags 
           that start with the elements of the list (e.g: "job_id,run_id")
         version_added: 2.6.0
         type: string
         example: job_id,run_id,dag_id,task_id
         default: job_id,run_id
   
   statsd_invert_allow_list:
         description: |
           Set to True to invert the functionality of statsd_invert_allow_list 
to a blocklist
         version_added: 2.6.0
         type: boolean
         example: ~
         default: "False"
   ```
   
   **statsd_disabled_tags** allows users to define a blocklist of tag name 
prefixes to disable.
   
   **statsd_invert_allow_list** is a boolean parameter that converts the 
functionality of statsd_invert_allow_list from an allowlist to a blocklist.
   
   The reason we need the metric name blocklist on top of a blocklist just for 
metric tags is because there are legacy metric names that have high cardinality 
under the definition explored in #29663 like: 
[`local_task_job.task_exit.<job_id>.<dag_id>.<task_id>.<return_code>`](https://github.com/apache/airflow/blob/main/airflow/jobs/local_task_job.py#L292)
 that users might want to disable to reduce their metric storage costs.


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