mixmaxhq/custody

Process state says "RUNNING" even if service has crashed

wearhere opened this issue · 3 comments

wearhere commented

This is because the processes we run are typically build (gulp) processes, that launch and monitor child webserver processes (using gulp-nodemon). When the webserver crashes, gulp remains healthy, and developers are none the wiser.

Implementation ideas are discussed here.

wearhere commented

@gaastonsr if you

  1. check out https://github.com/mixmaxhq/custody/tree/enhanced_statuses and https://github.com/mixmaxhq/contacts/tree/enhanced_process_status,
  2. restart contacts,
  3. and start custody

you'll see a special message flash in the state column 😉

gaastonsr commented 
<blink>hello gaston</blink>

🙂

  • 😄1
wearhere commented

Moved implementation ideas to https://github.com/mixmaxhq/custody/wiki/custody-probe and added some more ideas