You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2015/05/11 20:30:00 UTC
[jira] [Updated] (MESOS-2485) Add ability to distinguish slave
removals metrics by reason.
[ https://issues.apache.org/jira/browse/MESOS-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone updated MESOS-2485:
------------------------------
Sprint: Twitter Mesos Q1 Sprint 6, Twitter Q2 Sprint 1 - 4/13, Twitter Q2 Sprint 2, Twitter Q2 Sprint 3 - 5/11 (was: Twitter Mesos Q1 Sprint 6, Twitter Q2 Sprint 1 - 4/13, Twitter Q2 Sprint 2)
> Add ability to distinguish slave removals metrics by reason.
> ------------------------------------------------------------
>
> Key: MESOS-2485
> URL: https://issues.apache.org/jira/browse/MESOS-2485
> Project: Mesos
> Issue Type: Improvement
> Components: master
> Reporter: Benjamin Mahler
> Assignee: Benjamin Mahler
> Labels: twitter
>
> Currently we only expose a single removal metric ({{"master/slave_removals"}}) which makes it difficult to distinguish between removal reasons in the alerting.
> Currently, a slave can be removed for the following reasons:
> # Health checks failed.
> # Slave unregistered.
> # Slave was replaced by a new slave (on the same endpoint).
> In the case of (2), we expect this to be due to maintenance and don't want to be notified as strongly as with health check failures.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)