[checkmk-commits] Check_MK Git: check_mk: Updated bug entries #0792, #0793, #0794, #0791

Module: check_mk Branch: master Commit: e804841c3930c292db8edb152d5d52097defb2ef URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=e804841c3930c2… Author: Mathias Kettner <mk(a)mathias-kettner.de> Date: Fri Oct 12 16:15:06 2012 +0200 Updated bug entries #0792, #0793, #0794, #0791 --- .bugs/791 | 9 +++++++++ .bugs/792 | 9 +++++++++ .bugs/793 | 12 ++++++++++++ .bugs/794 | 12 ++++++++++++ 4 files changed, 42 insertions(+), 0 deletions(-) diff --git a/.bugs/791 b/.bugs/791 new file mode 100644 index 0000000..60fe8ec --- /dev/null +++ b/.bugs/791 @@ -0,0 +1,9 @@ +Title: Added check parameters/levels for uptime check +Component: checks +State: open +Date: 2012-10-12 16:10:17 +Targetversion: future +Class: feature + +The uptime check could have optional levels, so that a server goes +warning for e.g. 30 minutes after a reboot. diff --git a/.bugs/792 b/.bugs/792 new file mode 100644 index 0000000..cce182b --- /dev/null +++ b/.bugs/792 @@ -0,0 +1,9 @@ +Title: WATO access to service_descriptions +Component: wato +State: open +Date: 2012-10-12 16:11:07 +Targetversion: future +Class: feature + +WATO could give access to the variable service_descriptions in order +to rename services. diff --git a/.bugs/793 b/.bugs/793 new file mode 100644 index 0000000..4f04732 --- /dev/null +++ b/.bugs/793 @@ -0,0 +1,12 @@ +Title: Allow to rename services in a free an flexible way +Component: core +State: open +Date: 2012-10-12 16:11:54 +Targetversion: future +Class: feature + +Currently services can only partially be renamed. For example you +can change fs_%s to "Filesystem %s". It would be nice to be +able to rename "LOG /u01/app/oracle/tools/log/rman.log" -> "BCK-ORA rman.log" +It is not clear what impact such a feature has on the core and WATO, on +PNP Templates an the like. diff --git a/.bugs/794 b/.bugs/794 new file mode 100644 index 0000000..99a18ca --- /dev/null +++ b/.bugs/794 @@ -0,0 +1,12 @@ +Title: Temporarily deactivate active checks in WATO +Component: wato +State: open +Date: 2012-10-12 16:13:51 +Targetversion: future +Class: feature + +WATO could offer the possibility for active checks (legacy checks, custom checks) to +be currently deactivated. Such checks would then completely vanish from Nagios +and the status GUI but would remain in the configuration so they could easily +be activated again later. This is not the same as deactivating active checks +in Nagios.