Hi all, This follows up on the earlier [DISCUSS] thread on the configuration design for the REST API & UI metrics tagging feature (PR #64523):
https://lists.apache.org/thread/2o3g4yvr0pzr64fzjwf9xd78obd4dhnt Thanks everyone for the thoughtful input. The discussion has clearly converged on Option B, with support from Vincent, ashb, Niko, Pierre, and Jarek. Based on that, I’d like to call a lazy consensus on the following design for PR #64523: - Route-to-tag mappings are hardcoded in Airflow core (no user-configurable JSON mapping). - Following Vincent’s suggestion, we drop the proxy-name mapping entirely and use the API path directly as the metric tag. - Users get a simple boolean flag to enable/disable the metrics middleware. The lazy consensus will be reached in 72 hours on: July 10, 2026, 13:00 UTC. No need to reply unless you object to the proposal. Thanks, Henry
