Michael Barrett
Michael Barrett
Right now you can only specify a regex for the ID of an alert for suppressions. This works in some cases, but in a lot of other cases it'd be...
Currently once something is recorded in the state database it's there forever. An example of when this is bad: - You launch an instance and configure it to be monitored...
Per this: http://nagios.sourceforge.net/docs/3_0/statetypes.html When we get a soft failure state, then an OK failure state (which will be soft), and then finally go to a HARD/OK state no notification should...
Should be pretty easy to make this a configurable thing, and people may find it useful.
The reactor should only give handlers so much time (configurable) to handle a result.
This bit of code: ``` if os.path.isfile(f): logger.debug("Parsing include (%s:%d): %s", filename, lineno, f) c.extend(recursive_preprocess(f)) else: logger.warning("%s is not a regular file, " "skipping (%s:%d).", f, filename, lineno) ``` Will...
The base groundwork is there for allowing for configuration propagation, but there's still a lot of work to be done. It'd be great if the scheduler pushed it's config +...
It'd be good to have a way to run passive checks (ie: non-probe based monitors - useful for monitoring stats or events in some systems) and submit them into the...