mik-laj commented on a change in pull request #14537: URL: https://github.com/apache/airflow/pull/14537#discussion_r584468647
########## File path: docs/apache-airflow/logging-monitoring/check-health.rst ########## @@ -20,7 +20,13 @@ Checking Airflow Health Status ============================== -Airflow has s two methods to check the health of components - HTTP checks and CLI checks. Their choice depends on the role of the component as well as what tools it uses to monitor the deployment. +Airflow has two methods to check the health of components - HTTP checks and CLI checks. Their choice depends on the role of the component as well as what tools it uses to monitor the deployment. + +For example, when running on Kubernetes, use `a Liveness probes <https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/>`__ (``livenessProbe`` property) with :ref:`CLI checks <check-health/cli-checks-for-scheduler>`__ on the scheduler deployment to restart it when it fail. For the webserver, you can configure the readiness probe (``readinessProbe`` property) using :ref:`check-health/http-endpoint`. + +For an example for a Docker Compose environment, see the ``docker-compose.yaml`` file available in the :doc:`/start/docker.rst`. Review comment: ```suggestion For an example for a Docker Compose environment, see the ``docker-compose.yaml`` file available in the :doc:`/start/docker`. ``` ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
