Flapjack's Architecture

Check lifecycle

  1. create check in admin interface
  2. clear jobs on beanstalkd
  3. run flapjack-populator
  4. check is run by flapjack-worker
    1. result is written onto beanstalkd
    2. check is written back on beanstalkd with a delay
  5. result is processed by flapjack-worker
    • if the check is failing
      1. user is notified if the check's parents aren't failing
      2. event is created from result and persisted