You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "David Robinson (JIRA)" <ji...@apache.org> on 2015/07/09 01:47:04 UTC

[jira] [Created] (MESOS-3022) export additional metrics from scheduler driver

David Robinson created MESOS-3022:
-------------------------------------

             Summary: export additional metrics from scheduler driver
                 Key: MESOS-3022
                 URL: https://issues.apache.org/jira/browse/MESOS-3022
             Project: Mesos
          Issue Type: Improvement
            Reporter: David Robinson
            Priority: Minor


The scheduler driver only exports the metrics below, but ideally it would export its version and a count of messages by message type.

{code}
$ curl -s localhost:20902/metrics/snapshot | python -m json.tool
{
    "scheduler/event_queue_dispatches": 0,
    "scheduler/event_queue_messages": 0,
    "system/cpus_total": 24,
    "system/load_15min": 0.49,
    "system/load_1min": 0.36,
    "system/load_5min": 0.46,
    "system/mem_free_bytes": 269713408,
    "system/mem_total_bytes": 33529266176
}
{code}

The scheduler driver version could be used during troubleshooting to identify frameworks that are using an old, potentially backwards incompatible, scheduler driver (eg, a framework hasn't been restarted after a Mesos deploy, so it still links against an old incompatible libmesos).

A count of messages by message type would help identify a problem w/ a specific feature, eg task reconciliation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)