KulykDmytro opened a new issue, #23513:
URL: https://github.com/apache/airflow/issues/23513
### Apache Airflow version
2.2.5
### What happened
Setting `FLOWER_TASK_RUNTIME_METRIC_BUCKETS` container's env variable via
extraEnv in chart not causing to change metric's bucketing
```yaml
extraEnv: |
- name: FLOWER_PURGE_OFFLINE_WORKERS
value: "300"
- name: FLOWER_TASK_RUNTIME_METRIC_BUCKETS
value: 1,2.5,5,10,30,60,120,300,inf
```
outputs over flower's `/metrics`
```
flower_task_runtime_seconds_bucket{le="0.005",task="airflow.executors.celery_executor.execute_command",worker="celery@airflow-official-worker-64dbd9bb4-tgrzk"}
0.0
flower_task_runtime_seconds_bucket{le="0.01",task="airflow.executors.celery_executor.execute_command",worker="celery@airflow-official-worker-64dbd9bb4-tgrzk"}
0.0
flower_task_runtime_seconds_bucket{le="0.025",task="airflow.executors.celery_executor.execute_command",worker="celery@airflow-official-worker-64dbd9bb4-tgrzk"}
0.0
flower_task_runtime_seconds_bucket{le="0.05",task="airflow.executors.celery_executor.execute_command",worker="celery@airflow-official-worker-64dbd9bb4-tgrzk"}
0.0
flower_task_runtime_seconds_bucket{le="0.075",task="airflow.executors.celery_executor.execute_command",worker="celery@airflow-official-worker-64dbd9bb4-tgrzk"}
0.0
flower_task_runtime_seconds_bucket{le="0.1",task="airflow.executors.celery_executor.execute_command",worker="celery@airflow-official-worker-64dbd9bb4-tgrzk"}
0.0
flower_task_runtime_seconds_bucket{le="0.25",task="airflow.executors.celery_executor.execute_command",worker="celery@airflow-official-worker-64dbd9bb4-tgrzk"}
0.0
flower_task_runtime_seconds_bucket{le="0.5",task="airflow.executors.celery_executor.execute_command",worker="celery@airflow-official-worker-64dbd9bb4-tgrzk"}
0.0
flower_task_runtime_seconds_bucket{le="0.75",task="airflow.executors.celery_executor.execute_command",worker="celery@airflow-official-worker-64dbd9bb4-tgrzk"}
0.0
flower_task_runtime_seconds_bucket{le="1.0",task="airflow.executors.celery_executor.execute_command",worker="celery@airflow-official-worker-64dbd9bb4-tgrzk"}
0.0
flower_task_runtime_seconds_bucket{le="2.5",task="airflow.executors.celery_executor.execute_command",worker="celery@airflow-official-worker-64dbd9bb4-tgrzk"}
0.0
flower_task_runtime_seconds_bucket{le="5.0",task="airflow.executors.celery_executor.execute_command",worker="celery@airflow-official-worker-64dbd9bb4-tgrzk"}
5.0
flower_task_runtime_seconds_bucket{le="7.5",task="airflow.executors.celery_executor.execute_command",worker="celery@airflow-official-worker-64dbd9bb4-tgrzk"}
5.0
flower_task_runtime_seconds_bucket{le="10.0",task="airflow.executors.celery_executor.execute_command",worker="celery@airflow-official-worker-64dbd9bb4-tgrzk"}
11.0
flower_task_runtime_seconds_bucket{le="+Inf",task="airflow.executors.celery_executor.execute_command",worker="celery@airflow-official-worker-64dbd9bb4-tgrzk"}
11.0
```
### What you think should happen instead
Based on [flower
documentation](https://github.com/mher/flower/blob/df87aec34d74a70fa6055105f27fbab2296334d9/docs/config.rst#id64)
flower metric's histogram buckets can be set over env variable
`FLOWER_TASK_RUNTIME_METRIC_BUCKETS`
### How to reproduce
use official chart
set `FLOWER_TASK_RUNTIME_METRIC_BUCKETS` value over `extraEnv`
### Operating System
.4.181-99.354.amzn2.x86_64 #1 SMP Wed Mar 2 18:50:46 UTC 2022 x86_64
GNU/Linux
### Versions of Apache Airflow Providers
_No response_
### Deployment
Official Apache Airflow Helm Chart
### Deployment details
Amazon EKS
### Anything else
`FLOWER_PURGE_OFFLINE_WORKERS` setting takes it's effect instead
### 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]
