You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2017/12/04 22:14:00 UTC
[jira] [Updated] (MESOS-4664) Add allocator metrics.
[ https://issues.apache.org/jira/browse/MESOS-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Mahler updated MESOS-4664:
-----------------------------------
Description:
There are currently no metrics that provide visibility into the allocator, except for the event queue size. This makes monitoring an debugging allocation behavior in a multi-framework setup difficult.
Some thoughts for initial metrics to add:
* How many allocation runs have completed? (counter): MESOS-4718
* How many offers has each role / framework received? (counter): MESOS-4719
* Current allocation breakdown: allocated / available / total (gauges): MESOS-4720
* Current maximum shares (gauges): MESOS-4724
* How many active filters are there for the role / framework? (gauges): MESOS-4722
* How many frameworks are suppressing offers? (gauges)
* How long does an allocation run take? (timers): MESOS-4721
* Maintenance related metrics:
** How many maintenance events are active? (gauges)
** How many maintenance events are scheduled but not active (gauges)
* Quota related metrics:
** How much quota is set for each role? (gauges)
** How much quota is satisfied? How much unsatisfied? (gauges): MESOS-4723
Some of these are already exposed from the master's metrics, but we should not assume this within the allocator.
was:
There are currently no metrics that provide visibility into the allocator, except for the event queue size. This makes monitoring an debugging allocation behavior in a multi-framework setup difficult.
Some thoughts for initial metrics to add:
* How many allocation runs have completed? (counter): MESOS-4718
* How many allocations each framework got? (counter): MESOS-4719
* Current allocation breakdown: allocated / available / total (gauges): MESOS-4720
* Current maximum shares (gauges): MESOS-4724
* How many active filters are there for the role / framework? (gauges): MESOS-4722
* How many frameworks are suppressing offers? (gauges)
* How long does an allocation run take? (timers): MESOS-4721
* Maintenance related metrics:
** How many maintenance events are active? (gauges)
** How many maintenance events are scheduled but not active (gauges)
* Quota related metrics:
** How much quota is set for each role? (gauges)
** How much quota is satisfied? How much unsatisfied? (gauges): MESOS-4723
Some of these are already exposed from the master's metrics, but we should not assume this within the allocator.
> Add allocator metrics.
> ----------------------
>
> Key: MESOS-4664
> URL: https://issues.apache.org/jira/browse/MESOS-4664
> Project: Mesos
> Issue Type: Epic
> Components: allocation
> Reporter: Benjamin Mahler
> Assignee: Benjamin Bannier
> Priority: Critical
>
> There are currently no metrics that provide visibility into the allocator, except for the event queue size. This makes monitoring an debugging allocation behavior in a multi-framework setup difficult.
> Some thoughts for initial metrics to add:
> * How many allocation runs have completed? (counter): MESOS-4718
> * How many offers has each role / framework received? (counter): MESOS-4719
> * Current allocation breakdown: allocated / available / total (gauges): MESOS-4720
> * Current maximum shares (gauges): MESOS-4724
> * How many active filters are there for the role / framework? (gauges): MESOS-4722
> * How many frameworks are suppressing offers? (gauges)
> * How long does an allocation run take? (timers): MESOS-4721
> * Maintenance related metrics:
> ** How many maintenance events are active? (gauges)
> ** How many maintenance events are scheduled but not active (gauges)
> * Quota related metrics:
> ** How much quota is set for each role? (gauges)
> ** How much quota is satisfied? How much unsatisfied? (gauges): MESOS-4723
>
> Some of these are already exposed from the master's metrics, but we should not assume this within the allocator.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)