Flapjack's Architecture
Check lifecycle
- create check in admin interface
- clear jobs on beanstalkd
- run flapjack-populator
- check is run by flapjack-worker
- result is written onto beanstalkd
- check is written back on beanstalkd with a delay
- result is processed by flapjack-worker
- if the check is failing
- user is notified if the check's parents aren't failing
- event is created from result and persisted
Except where otherwise noted, content on this wiki is licensed under the following license:CC Attribution-Share Alike 3.0 Unported
