zoomingrocket opened a new issue, #73349: URL: https://github.com/apache/airflow/issues/73349
### Under which category would you file this issue? Airflow Core ### Apache Airflow version 3.3.1 ### What happened and how to reproduce it? We upgraded our local pyPI install from Airflow v3.1.8 to v3.3.1. Our monitoring services use the local health check endpoint exposed via scheduler mini HTTP Server to keep track of all individual schedulers in a HA system and post upgrade, though schedulers were running fine all our health checks were failing. After further diagnostics, it was clear that there is no longer HTTP Health check server running; the airflow.cfg has below properties setup properly. I checked latest docs and seems like this is valid and supported path? https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/logging-monitoring/check-health.html#scheduler-health-check-server [scheduler] enable_health_check = True scheduler_health_check_server_host = 0.0.0.0 scheduler_health_check_server_port = 8974 ### What you think should happen instead? Local mini health check path should be listening on the port configured as described in documentation: https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/logging-monitoring/check-health.html#scheduler-health-check-server ### Operating System RHEL 9.x ### Deployment Virtualenv installation ### Apache Airflow Provider(s) _No response_ ### Versions of Apache Airflow Providers _No response_ ### Official Helm Chart version Not Applicable ### Kubernetes Version _No response_ ### Helm Chart configuration _No response_ ### Docker Image customizations _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]
