You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2017/09/21 19:57:00 UTC

[jira] [Comment Edited] (MESOS-7999) Add and document ability to expose new /monitor modules on agents

    [ https://issues.apache.org/jira/browse/MESOS-7999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16175118#comment-16175118 ] 

James Peach edited comment on MESOS-7999 at 9/21/17 7:56 PM:
-------------------------------------------------------------

You can write an anonymous Mesos module that uses the lib process [metrics|https://github.com/apache/mesos/blob/master/3rdparty/libprocess/include/process/metrics/metrics.hpp#L94] API to expose metrics into {{/metrics/snapshot}}.


was (Author: jamespeach):
You can write an anonymous Mesos module that uses the lib process [metrics|https://github.com/apache/mesos/blob/master/3rdparty/libprocess/include/process/metrics/metrics.hpp#L94] API to expose metrics into {{/metrics/snapshot}}/

> Add and document ability to expose new /monitor modules on agents
> -----------------------------------------------------------------
>
>                 Key: MESOS-7999
>                 URL: https://issues.apache.org/jira/browse/MESOS-7999
>             Project: Mesos
>          Issue Type: Wish
>          Components: agent, json api, modules, statistics
>            Reporter: Charles Allen
>
> When looking at how to collect data about the cluster, the best way to support functionality similar to Kubernetes DaemonSets is not completely clear.
> One key use case fore DaemonSets is a monitor for system metrics. This ask is that agents are able to have a module which either exposes new endpoints in {{/monitor}} or allows pluggable entries to be added to {{/monitor/statistics}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)