You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If any of the participants in a Msgflo graph deadlocks, or for other reasons* stop to process/send messages, the system will generally fail to perform intended function.
By monitoring the queues that represent the output of the system, we could detect this.
msgflo-monitor --queue sensor.NEWVALUE --expect-periodic 1s --fail-missed 3
Process should probably exit (with non-zero code) on failure. Then one can use for instance in systemd OnFailure=myservice-restart.service to try to recover.
Alternatively it may be useful if it writes a single line on stdout, or can execute some command.
For systems that don't produce data periodically by nature, it is recommended that there is a process generating test message periodically.
To have a chain of trust, the msgflo-monitor program should ideally also be monitored. For instance by using the watchdog feature of systemd.
* crashing process and restarting it usually well handled by the service management already, be it Heroku or systemd (#20).
The text was updated successfully, but these errors were encountered:
If any of the participants in a Msgflo graph deadlocks, or for other reasons
*
stop to process/send messages, the system will generally fail to perform intended function.By monitoring the queues that represent the output of the system, we could detect this.
msgflo-monitor --queue sensor.NEWVALUE --expect-periodic 1s --fail-missed 3
Process should probably exit (with non-zero code) on failure. Then one can use for instance in systemd
OnFailure=myservice-restart.service
to try to recover.Alternatively it may be useful if it writes a single line on stdout, or can execute some command.
For systems that don't produce data periodically by nature, it is recommended that there is a process generating test message periodically.
To have a chain of trust, the msgflo-monitor program should ideally also be monitored. For instance by using the watchdog feature of systemd.
*
crashing process and restarting it usually well handled by the service management already, be it Heroku or systemd (#20).The text was updated successfully, but these errors were encountered: