Age | Commit message (Collapse) | Author | Files | Lines |
|
This allows to view all the important checks for a group much easier.
|
|
|
|
There was an issue with the select all in that clicking an input field
didn't trigger the marking as the event was not pushed through to the
underlying elements.
|
|
This commit adds a select all function to select all rows of a list to
mark them all.
This could be used to send a refresh to all these checks or acknowledge
them or whatever.
Also the referrer handling in checkAction() was moved to the start so
that even with an error the same thing happens.
|
|
The field name was wrong and therefore actions weren't completed and the
redirect was wrong.
|
|
Because Firefox has no attribute path for an event to represent the
element chain of the target, we need to iterate through the parents.
|
|
The selected rows are now properly highlighted. See #7 for more
information.
|
|
As in #7 requested, it is now possible to select a row by clicking on
the row itself. This should make it much easier to select a larger
number of rows.
|
|
This way it is possible to jump between a node and its checks.
|
|
Somewhen in the last couple years, something called a referer policy was
introduced. This avoided the correct relocation after any action was
sent.
Now with the fix, the redirect properly works.
|
|
This adds the first basic listing of notifications to the check details.
No idea how many of them should be listed here, but having the list at
all for a start should be okay.
|
|
There is just no information that could possibily be shown there, that
isn't already shown somewhere else.
|
|
When a check is acknowledged, no more further notifications should be
sent. But for the notified system, it should be made clean, that it is
taken care of and no further actions need to be done, therefore send an
okay, even when the check isn't okay.
|
|
The adding of the order by clause happend in the wrong position and
therefore made the resultset unuseable.
|
|
The result list should be ordered for the state when unhandled entries
should be returned. Else it is getting weird to figure out, which issue
is the most important to fix.
|
|
With some monitors, the view may be too wide to make out, which line
belongs to what. For that purpose, add a background color when the mouse
is hovering over a line.
|
|
Now all the fields are shown in a column like view, which makes viewing
them much nicer to the eye.
|
|
This adds a detail view for a single check. The purpose is to view
notifications for this check alone and get the context information on
the node it belongs to, the command and settings.
|
|
This is related to #6. The muting, enable and disable were not working
properly, because the date was not set when the check was updated.
With this comes also the first icon to represent the muted status.
|
|
Monfront now has a basic search functionality for nodes. It also got
some nicer design to make it more useable.
|
|
This is the first step to view the group status. The templates were
split into multipe parts, to make reuse easier.
|
|
After the notifications were extracted the mute option didn't work
anymore. With this fix, they are back to working.
|
|
This will be replaced with a different system in the long term.
|
|
The unhandled checks didn't contain the mapping id, which caused an
error at scan time.
|
|
This finally adds a reload to the frontend, so that one hasn't to reload
manually all the time.
|
|
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.
|
|
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 will return the unhandled groups/checks/whatever but is still work
in progress.
|
|
This version can already show the list of checks, their last state and
add ways to manipulate the check or active check.
|