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

Benjamin Mahler commented on MESOS-2485:
----------------------------------------

https://reviews.apache.org/r/33152/
https://reviews.apache.org/r/33153/
https://reviews.apache.org/r/33154/
https://reviews.apache.org/r/33155/

> 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)

Reply via email to