[
https://issues.apache.org/jira/browse/MESOS-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793090#comment-13793090
]
Joe Smith commented on MESOS-433:
---------------------------------
"Of course, there are likely many frameworks that will need to implement this,
so it may very well be something we should implement.."
This is absolutely suggesting that Mesos steps up and participates as part of
the observability stack.
Pushing this down into a feature provided by Mesos would be a _huge_ benefit to
each framework/executor that runs on top of it, and prevent a lot of wheels
from being re-invented. In addition, it decreases the number of places that an
OBS stack needs to check from per-task to per-host, which is my primary concern
here.
+1 from me
> add exportStats method to executor
> ----------------------------------
>
> Key: MESOS-433
> URL: https://issues.apache.org/jira/browse/MESOS-433
> Project: Mesos
> Issue Type: Story
> Components: slave, webui
> Reporter: brian wickman
>
> Now that the slave exports per-executor stats via the UI, the slave should be
> able to periodically request application-specific stats from the executor
> (e.g. zookeeper session id, connection counts, whatever) and export them on
> the executor's behalf. This way we don't need to reinvent any observability
> wheels.
> The interface could either be exportStats(task_id) or just exportStats(), and
> return a JSON object with all stats to export.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
