Incident log

Transcript

1. Incident Log Log activity events for incidents : Opened Closed Reopned Resolved Escalated Snoozed Commented
2. Input Patterns Rabbit queue events { t y p e : ' i n c i d e n t # c o m m e n t e d ' , o r g a n i z a t i o n : ' b i g p a n d a ' , u s e r : ' g u y @ b i g p a n d a . i o ' , t i m e s t a m p : 1 2 3 4 5 , d a t a : { i d : ' 1 2 3 4 5 6 ' , p a r a m s : { p e r f o r m e r : ' g u y @ b i g p a n d a . i o ' , c o m m e n t : ' c o o l p r e s e n t a t i o n ' } } , _ m e t a d a t a : { s t a r t T i m e : + n e w D a t e ( ) } , s o u r c e : ' w e b - a p i ' } ;
3. Output Patterns Rest api a p p . g e t ( ' / i n c i d e n t - l o g / : i d ' , g e t L o g ) ; Stream publish event to 'incident‑log/output' web‑api consumes the event and streams to frontier using websockets.
4. Flaws and race conditions Comments do not exists outside of the log Data is duplicated Synchronize data between the log and the incident/actions