Return-Path: X-Original-To: apmail-mesos-issues-archive@minotaur.apache.org Delivered-To: apmail-mesos-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DCC9418D23 for ; Mon, 7 Dec 2015 19:36:17 +0000 (UTC) Received: (qmail 90718 invoked by uid 500); 7 Dec 2015 19:36:11 -0000 Delivered-To: apmail-mesos-issues-archive@mesos.apache.org Received: (qmail 90574 invoked by uid 500); 7 Dec 2015 19:36:11 -0000 Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list issues@mesos.apache.org Received: (qmail 90457 invoked by uid 99); 7 Dec 2015 19:36:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Dec 2015 19:36:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 2A0432C1F69 for ; Mon, 7 Dec 2015 19:36:11 +0000 (UTC) Date: Mon, 7 Dec 2015 19:36:11 +0000 (UTC) From: "Artem Harutyunyan (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (MESOS-4015) Expose task / executor health in master & slave state.json MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MESOS-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan reassigned MESOS-4015: ---------------------------------------- Assignee: Artem Harutyunyan > Expose task / executor health in master & slave state.json > ---------------------------------------------------------- > > Key: MESOS-4015 > URL: https://issues.apache.org/jira/browse/MESOS-4015 > Project: Mesos > Issue Type: Improvement > Affects Versions: 0.25.0 > Reporter: Sargun Dhillon > Assignee: Artem Harutyunyan > Priority: Trivial > Labels: mesosphere > > Right now, if I specify a healthcheck for a task, the only way to get to it is via the Task Status updates that come to the framework. Unfortunately, this information isn't exposed in the state.json either in the slave or master. It'd be ideal to have that information to enable tools like Mesos-DNS to be health-aware. -- This message was sent by Atlassian JIRA (v6.3.4#6332)