Module: check_mk
Branch: master
Commit: 840f6eccb38b3973fc59e3a9dfb955f9d93e5280
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=840f6eccb38b39…
Author: Florian Heigl <fh(a)mathias-kettner.de>
Date: Fri Sep 21 10:48:02 2012 +0200
Add new bug entry
---
.bugs/803 | 14 ++++++++++++++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/.bugs/803 b/.bugs/803
new file mode 100644
index 0000000..1001da2
--- /dev/null
+++ b/.bugs/803
@@ -0,0 +1,14 @@
+Title: Oracle Sessions should be able to define limits per Database
+Component: checks
+State: open
+Date: 2012-09-21 10:41:08
+Targetversion: 1.2.0
+Class: feature
+
+The oracle_sessions check has has warn/crit levels. If using WATO those can only
+be specified as a "global" value because no service name can be specified.
+A user tried to work around this using the inventory->ruleset shortcut but that
+didn't help either.
+
+We should change the WATO interface for the check, to make it support the
+same configuration as is available on the CLI-side of things.