You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Bruno Bonagura (JIRA)" <ji...@apache.org> on 2018/03/09 15:51:01 UTC

[jira] [Comment Edited] (AIRFLOW-1084) `/health` endpoint on each component

    [ https://issues.apache.org/jira/browse/AIRFLOW-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393038#comment-16393038 ] 

Bruno Bonagura edited comment on AIRFLOW-1084 at 3/9/18 3:50 PM:
-----------------------------------------------------------------

It's very needed for distributed (Celery) infrastructures. How else will the operations team know whether a worker is running fine?


was (Author: bbonagura9):
It's very needed for distributed (Celery) infrastructures. How else will the operations team know whether the a worker is running fine?

> `/health` endpoint on each component
> ------------------------------------
>
>                 Key: AIRFLOW-1084
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1084
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Semet
>            Priority: Major
>
> Please provide a {{/health}} endpoint of each of the following component: 
> - webservice (to avoid pinging the {{/}} root endpoint)
> - worker
> - scheduler
> This would ease integration in Mesos/Marathon framework. 
> If you agree, I volunteer to add this change.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)