SamWheating commented on code in PR #23905: URL: https://github.com/apache/airflow/pull/23905#discussion_r888434689
########## docs/apache-airflow/logging-monitoring/check-health.rst: ########## @@ -72,6 +72,19 @@ status of the application. The return code is only indicative of the state of th monitoring, then in case of failure of the web server, you will lose the ability to monitor scheduler, which means that it can be restarted even if it is in good condition. For greater confidence, consider using :ref:`CLI Check for Scheduler <check-health/cli-checks-for-scheduler>`. +.. _check-health/scheduler-health-check-server: + +Scheduler Health Check Server +------------------------- + +In order to check scheduler health independent of the webserver, Airflow optionally starts an small HTTP server +in each scheduler to serve a scheduler ``\health`` endpoint. It returns status code ``200`` when the scheduler +is healthy and status code ``503`` when the scheduler is unheatlhy. To run this server in each scheduler, set Review Comment: ```suggestion is healthy and status code ``503`` when the scheduler is unhealthy. To run this server in each scheduler, set ``` ########## docs/apache-airflow/logging-monitoring/check-health.rst: ########## @@ -72,6 +72,19 @@ status of the application. The return code is only indicative of the state of th monitoring, then in case of failure of the web server, you will lose the ability to monitor scheduler, which means that it can be restarted even if it is in good condition. For greater confidence, consider using :ref:`CLI Check for Scheduler <check-health/cli-checks-for-scheduler>`. +.. _check-health/scheduler-health-check-server: + +Scheduler Health Check Server +------------------------- + +In order to check scheduler health independent of the webserver, Airflow optionally starts an small HTTP server Review Comment: ```suggestion In order to check scheduler health independent of the webserver, Airflow optionally starts a small HTTP server ``` -- 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]
