Module: check_mk
Branch: master
Commit: 61cb7e7436a46529ad8ffe2f61bc38b0bc138da9
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=61cb7e7436a465…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Mon Jun 4 12:22:40 2012 +0200
Updated bug entries #0763
---
.bugs/763 | 23 +++++++++++++++++++++++
1 files changed, 23 insertions(+), 0 deletions(-)
diff --git a/.bugs/763 b/.bugs/763
new file mode 100644
index 0000000..567972f
--- /dev/null
+++ b/.bugs/763
@@ -0,0 +1,23 @@
+Title: Duplicate Check on Cisco 4500
+Component: checks
+State: open
+Date: 2012-06-04 12:20:55
+Targetversion: future
+Class: nastiness
+
+Generating Nagios configuration...Configuration Error: ERROR:
+Duplicate service description 'Temperature Chassis Temperature Sensor'
+for host 'cat_4500_1'!
+
+- 1st occurrance: checktype = cisco_temp_perf, item = 'Chassis
+Temperature Sensor'
+
+- 2nd occurrance: checktype = cisco_temp_sensor, item = 'Chassis
+Temperature Sensor'
+
+Can we invent something in Check_MK that automatically drops
+duplicate services? How can a precedence be implemented? Should
+we at least issue a warning? Should this be checked during
+inventory? The service description is known at this point of
+time and a check for duplicates could be done and the new duplicate
+checks ignored.