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

   ### Apache Airflow version
   
   Other Airflow 3 version (please specify below)
   
   ### If "Other Airflow 3 version" selected, which one?
   
   3.1.1
   
   ### What happened?
   
   Pool names can take any character, for example:
   `pool name with whitespace and emoji😎` is a valid pool name.
   
   However, this will raise an `InvalidStatsNameException` when reporting 
metrics such as:
   ```
   2025-12-30T10:47:28.000732Z [error    ] Invalid stat name: 
pool.deferred_slots.pool name with whitespace and emoji😎 table. 
[airflow.metrics.validators] loc=validators.py:125
   airflow.exceptions.InvalidStatsNameException: The stat name 
(pool.running_slots.pool name with whitespace and emoji😎) has to be composed of 
ASCII alphabets, numbers, or the underscore, dot, or dash characters.
   ```
   
   ### What you think should happen instead?
   
   Valid pool names should report metrics too, and not cause an 
`InvalidStatsNameException`. Thinking out loud, we could:
   - Transform the name into a valid stat name (maybe cause a breaking change?)
   - Report metrics using the pool id instead (likely a breaking change + 
difficult to link back the pool name?)
   - ....?
   
   ### How to reproduce
   
   See above
   
   ### Operating System
   
   N/A
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Astronomer
   
   ### 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