Hi, Has anyone thought about the idea of building some kind of event bus (similar to what Marathon provided) directly inside Mesos?
What I roughly have in mind: 1. The HTTP API effort already defined a very rich set of events, which Mesos master/agent could send to scheduler/executor; 2. We could build an HTTP endpoint like `/v1/events`, which utilizes the same mechanism of HTTP scheduler/executor API and allows a *subscriber* to subscribe to event streams; 3. Some kind of filter rules as well as authorization is definitely needed for both reducing traffic and enforce ACL. Possible use cases I could image: 1. Pipe event streams to external database for analysis/archiving; 2. Faster notification to external service discovery systems like Mesos-DNS w/o requiring it to poll /state from master; 3. Notification to other long running daemons for newly launched/killed tasks at a Mesos agent Please let me know what you think. Thanks! -- Cheers, Zhitao Li
