| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
This should enable the notifier to make a decent decision on what to do.
|
|
This adds mapping levels to the check runner. When the exit code is
returned, the actual level is looked up using the configured mapping.
After that, the state is entered into the table and added the same way
to the notifications.
|
|
This allows to map the command exit codes to any other output level
which can then be reported by the notification plugin.
With the provided colors, the frontend will show them accordingly.
|
|
This change triggers updates for checks when a node or command was
updated. This way everything gets adjusted without much work.
|
|
This still needs some cleanup, but oh well. The most important thing is,
that it works for now.
|
|
New checks were not added to the active_checks, because they were never
touched before.
|
|
It would have been nice to use rowgrouping for the node name, but
somehow it wasn't easy to get the rowcount. So this should do for now.
|
|
This adds the path environment configuration to control which programs
to call.
|
|
This will return the unhandled groups/checks/whatever but is still work
in progress.
|
|
|
|
Before the timeout for checks was static. With this change it is finally
an option to configure.
|
|
This version can already show the list of checks, their last state and
add ways to manipulate the check or active check.
|
|
An acknowledge should be set to false when the alarm switches to an ok
state.
|
|
|
|
|
|
This output was poluting the log and wasn't necessary.
|
|
The deadlines were wrong all over the place, so this commit finally
fixes that.
|
|
This server generates active checks from the check configuration.
|
|
With selecting only the bare minimum we get much nicer performance.
|
|
That constraint would hinder the addition of multiple notifications, so
it needs to be removed.
|
|
|
|
|
