When tasks fail or are lost, the accompanying StatusUpdate message from Mesos often contains a useful message that could help developers to debug their app or configuration. Marathon currently discards this information but it would be nicer to record it and make it accessible via the API.
- [ ] Filters for event subscribers
- [ ] Expose filters for http callback subscribers
- [ ] Bounded history storage that subscribes to a subset of events
- [x] Task failure history storage
- [x] Expose task failures via the API