[MESOS-2485] Add ability to distinguish slave removals metrics by reason.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.23.0
• Component/s: master
• Labels: twitter
• Target Version/s: 0.23.0
• Sprint: Twitter Mesos Q1 Sprint 6, Twitter Q2 Sprint 1 - 4/13, Twitter Q2 Sprint 2, Twitter Q2 Sprint 3 - 5/11
• Story Points: 3
• Assignee: Benjamin Mahler
• Reporter: Benjamin Mahler
• Shepherd: Vinod Kone
• Created: 12/Mar/15 19:44
• Updated: 21/May/15 18:31
• Resolved: 14/May/15 00:01

Description

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:

1. Health checks failed.
2. Slave unregistered.
3. 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.