[jira] [Assigned] (MESOS-4664) Add allocator metrics.
[ https://issues.apache.org/jira/browse/MESOS-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bannier reassigned MESOS-4664: --- Assignee: (was: Benjamin Bannier) > 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 >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 (v7.6.3#76005)
[jira] [Assigned] (MESOS-4664) Add allocator metrics.
[ https://issues.apache.org/jira/browse/MESOS-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Klaus Ma reassigned MESOS-4664: --- Assignee: Klaus Ma > Add allocator metrics. > -- > > Key: MESOS-4664 > URL: https://issues.apache.org/jira/browse/MESOS-4664 > Project: Mesos > Issue Type: Improvement > Components: allocation >Reporter: Benjamin Mahler >Assignee: Klaus Ma >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) > * Current allocation breakdown: allocated / available / total (gauges) > * Current maximum shares (gauges) > * How many active filters are there for the role / framework? (gauges) > * How many frameworks are suppressing offers? (gauges) > * How long does an allocation run take? (timers) > * 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) > > 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.3.4#6332)
[jira] [Assigned] (MESOS-4664) Add allocator metrics.
[ https://issues.apache.org/jira/browse/MESOS-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bannier reassigned MESOS-4664: --- Assignee: Benjamin Bannier > Add allocator metrics. > -- > > Key: MESOS-4664 > URL: https://issues.apache.org/jira/browse/MESOS-4664 > Project: Mesos > Issue Type: Improvement > 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) > * Current allocation breakdown: allocated / available / total (gauges) > * Current maximum shares (gauges) > * How many active filters are there for the role / framework? (gauges) > * How many frameworks are suppressing offers? (gauges) > * How long does an allocation run take? (timers) > * 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) > > 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.3.4#6332)
