You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Niklas Quarfot Nielsen (JIRA)" <ji...@apache.org> on 2015/01/14 23:49:35 UTC
[jira] [Comment Edited] (MESOS-2219) Add support for slave monitor
modules
[ https://issues.apache.org/jira/browse/MESOS-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277830#comment-14277830 ]
Niklas Quarfot Nielsen edited comment on MESOS-2219 at 1/14/15 10:49 PM:
-------------------------------------------------------------------------
What I had in mind was:
1) Create a Collector abstract interface (matches Monitor completely)
2) Rename Monitor -> MesosCollector or MesosMonitor
3) Have a Collector::create() which takes a slave command line flag and make the MesosMonitor/Collector the default one.
So yeah, no API change - just moving things around.
was (Author: nnielsen):
What I had in mind was:
1) Create a Collector interface (matches Monitor completely)
2) Rename Monitor -> MesosCollector or MesosMonitor
3) Have a Collector::create() which takes a slave command line flag and make the MesosMonitor/Collector the default one.
So yeah, no API change - just moving things around.
> Add support for slave monitor modules
> -------------------------------------
>
> Key: MESOS-2219
> URL: https://issues.apache.org/jira/browse/MESOS-2219
> Project: Mesos
> Issue Type: Task
> Components: slave
> Reporter: Niklas Quarfot Nielsen
>
> The monitor keeps track of container usage and can give valuable insight into the health of running tasks, resource slack and much more.
> Pluggable slave monitors (or collectors) could enable export of this information in interesting ways, for example push based models doing various forms of aggregation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)