- allow using a status key other than the message key, e.g. for plugins like disk space that monitor multiple resources - don't choke on an unknown status message - send a recovery message - don't track status of our own recover message or risk creating an infinite loop
if no config is specified on Dumper reactor rules, dump the entire message.
This is really a temporary fix. The longer-term fix is to create a single 'wubot' script that can run the monitors, reactors, or both.
- handle error that is a reference - prevent uninitialized value warning if no error available - error message logged at a higher level - these will now go to stdout by default