Module: check_mk
Branch: master
Commit: b1e6586522e8f371fd1e24849d24bf2af560f1ca
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=b1e6586522e8f3…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Tue Mar 1 18:30:21 2011 +0100
Updated bugs
---
.bugs/166 | 29 +++++++++++++++++++++++++++++
1 files changed, 29 insertions(+), 0 deletions(-)
diff --git a/.bugs/166 b/.bugs/166
new file mode 100644
index 0000000..5f9226c
--- /dev/null
+++ b/.bugs/166
@@ -0,0 +1,29 @@
+Title: legacy_checks could allow passive services
+Component: core
+Benefit: 1
+State: open
+Cost: 2
+Date: 2011-03-01 18:24:00
+Class: feature
+
+Chris Bowlby:
+> I'm not sure if anyone has mentioned this before, based on a cursory
+> search of the mailing list, but would be nice to have an optional
+> element that can be used as part of the legacy_check param that would
+> denote that particular service as being passive. For example:
+>
+> legacy_checks += [
+> ( ( "passive_check_command", "PASSIVE SERVCE", False,
True), ALL_HOSTS),
+> ( ( "active_check_command", "ACTIVE SERVCE", False),
ALL_HOSTS),
+> ( ( "active_check_command", "ACTIVE SERVCE2", False,
False), ALL_HOSTS),
+> ....
+> ]
+>
+> The example would set the first legacy check as passive, and the other
+> two as active. I know that one can simply use the extra_nagios_conf
+> parameter, but it's a wee bit clunky if you've got a large number of
+> passive checks and other elements that need to be converted. This idea
+> may provide a cleaner method where one can simply define the passive
+> check here, and allow them to take advantage of the other elements, such
+> as service groups, contact group links, etc. It also reduces the changes
+> of miss-creating an entry that causes a conflict later on.