Event hub
A platform for broadcasting and subscribing incidents or events
Use cases
- Service status/outage
- Property damage
- Alarm integrations
Service outage
- Shows the status of services
- Report outage
- Track outage resolve progress
Web service
| Time | Event |
|---|---|
| 10am | Our ES cluster encountered degraded performance, affecting usability of searching |
| 10:30am | ES cluster restarted, gradually recovering |
| 11:00am | ES back to normal |
ES outage
Trackwork
| Time | Event |
|---|---|
| 12/1/2016 1:00pm | track work starts |
| 12/1/2016 6:00pm | track work ends |
Western line trackwork
Property Damage
| Time | Type | Event |
|---|---|---|
| 11/1/2016 | start | Waterpipe broken |
| 12/1/2016 | event | Confirmed |
| 13/1/2016 | event | Fixing |
| 14/1/2016 | end | Resolved |
Minimal Valuable Product
- Twitter like subscribing mechanism for events/incidents
- Service and properties management
- API integration of events (bots)
Differentiation
- Evernote
- Zendesk
+ Only text (140 chars)
Event hub
+ Rich media
+ Followup events
+ Tree of event source
Zendesk
Ticket usually have only one receiver/subscriber
1-1 communication
Event hub
Events are subscribed by multiple users
1 - N broadcasting
incident hub
By James Deng
incident hub
- 390