[jira] [Created] (MESOS-6082) Add Call and Event based metrics to the master.

[Benjamin Mahler (JIRA)]

Benjamin Mahler created MESOS-6082:
--------------------------------------

             Summary: Add Call and Event based metrics to the master.
                 Key: MESOS-6082
                 URL: https://issues.apache.org/jira/browse/MESOS-6082
             Project: Mesos
          Issue Type: Improvement
          Components: master
            Reporter: Benjamin Mahler


Currently, the master only has metrics for the old-style messages and these are 
re-used for calls unfortunately:

{code}
  // Messages from schedulers.
  process::metrics::Counter messages_register_framework;
  process::metrics::Counter messages_reregister_framework;
  process::metrics::Counter messages_unregister_framework;
  process::metrics::Counter messages_deactivate_framework;
  process::metrics::Counter messages_kill_task;
  process::metrics::Counter messages_status_update_acknowledgement;
  process::metrics::Counter messages_resource_request;
  process::metrics::Counter messages_launch_tasks;
  process::metrics::Counter messages_decline_offers;
  process::metrics::Counter messages_revive_offers;
  process::metrics::Counter messages_suppress_offers;
  process::metrics::Counter messages_reconcile_tasks;
  process::metrics::Counter messages_framework_to_executor;
{code}

Now that we've introduced the Call/Event based API, we should have metrics that 
reflect this. For example:

{code}
{
  scheduler/calls: 100
  scheduler/calls/decline: 90,
  scheduler/calls/accept: 10,
  scheduler/calls/accept/operations/create: 1,
  scheduler/calls/accept/operations/destroy: 0,
  scheduler/calls/accept/operations/launch: 4,
  scheduler/calls/accept/operations/launch_group: 2,
  scheduler/calls/accept/operations/reserve: 1,
  scheduler/calls/accept/operations/unreserve: 0,
  scheduler/calls/kill: 0,
  // etc
}
{code}



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