Return-Path: X-Original-To: apmail-incubator-mesos-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-mesos-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AA2AD108BB for ; Thu, 11 Apr 2013 01:10:13 +0000 (UTC) Received: (qmail 52849 invoked by uid 500); 11 Apr 2013 01:10:13 -0000 Delivered-To: apmail-incubator-mesos-dev-archive@incubator.apache.org Received: (qmail 52813 invoked by uid 500); 11 Apr 2013 01:10:13 -0000 Mailing-List: contact mesos-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mesos-dev@incubator.apache.org Delivered-To: mailing list mesos-dev@incubator.apache.org Received: (qmail 52796 invoked by uid 99); 11 Apr 2013 01:10:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Apr 2013 01:10:13 +0000 Date: Thu, 11 Apr 2013 01:10:13 +0000 (UTC) From: "Benjamin Mahler (JIRA)" To: mesos-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (MESOS-432) Export percentage of allocation based monitoring data. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Benjamin Mahler created MESOS-432: ------------------------------------- Summary: Export percentage of allocation based monitoring data. Key: MESOS-432 URL: https://issues.apache.org/jira/browse/MESOS-432 Project: Mesos Issue Type: Task Reporter: Benjamin Mahler Assignee: Benjamin Mahler It is probably more useful for users to see the percentage of their allocation being used, instead of the raw cpu and memory data. This is also potentially useful for future oversubscription algorithms. The resource monitor should compute the percentage of the allocation for cpu/memory and export that as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira