Module: check_mk
Branch: master
Commit: 379049875753d2d0c6451ba40f4110fa0953e582
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=379049875753d2…
Author: Götz Golla <gg(a)mathias-kettner.de>
Date: Fri Sep 27 11:39:58 2013 +0200
check man page for new check "APC self test"
---
checkman/apc_symmetra_test | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/checkman/apc_symmetra_test b/checkman/apc_symmetra_test
new file mode 100644
index 0000000..396109e
--- /dev/null
+++ b/checkman/apc_symmetra_test
@@ -0,0 +1,27 @@
+title: APC self test
+agents: snmp
+catalog: hw/power
+license: GPL
+distribution: check_mk
+description:
+ This check monitors two OIDs of APC Symmetra UPS devices: The result of the last self test
+ and the last date of the self test run. The check becomes critical if the test result is
+ "failed" and it has a warning or ciritical state if the date of the last self test is more
+ than the warning or critical level ago.
+
+examples:
+ # sets the warning and critical levels to 5 and 10 days, respectively
+ ups_test_default = ( 5, 10 )
+
+inventory:
+ The inventory process checks if the device has a system description OIDs (.1.3.6.1.2.1.1.2.0)
+ and if the name of this OID is known to the test. If this is true the system is inventorized.
+
+[parameters]
+parameters(tuple): parameters is a tuple of two values
+
+ warn (int): The warning level in days
+ crit (int): The critical level in days
+
+[configuration]
+ups_test_default (tuple): This variable is preset to { (0,0) }
Module: check_mk
Branch: master
Commit: e94edf469a33bdaa3f6519065506343c9ccb1f02
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=e94edf469a33bd…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Fri Sep 27 11:21:00 2013 +0200
Updated bug entries #0992, #0993, #0994, #0995, #0991
---
.bugs/991 | 10 ++++++++++
.bugs/992 | 10 ++++++++++
.bugs/993 | 10 ++++++++++
.bugs/994 | 11 +++++++++++
.bugs/995 | 11 +++++++++++
5 files changed, 52 insertions(+)
diff --git a/.bugs/991 b/.bugs/991
new file mode 100644
index 0000000..d5513ab
--- /dev/null
+++ b/.bugs/991
@@ -0,0 +1,10 @@
+Title: LDAP Updates creates Auditlog entries with random user names
+Component: multisite
+State: open
+Date: 2013-09-27 11:02:23
+Targetversion: 1.2.3i3
+Class: nastiness
+
+Due to the cache every couple of minutes a random user might trigger
+an LDAP update and thus an entry in the audit log with his/her username.
+Better leave the user empty here or add some dummy entry.
diff --git a/.bugs/992 b/.bugs/992
new file mode 100644
index 0000000..0ff5aef
--- /dev/null
+++ b/.bugs/992
@@ -0,0 +1,10 @@
+Title: Notification spooling: only for certain plugin types or users
+Component: core
+State: open
+Date: 2013-09-27 11:15:30
+Targetversion: 1.4.0
+Class: feature
+
+It would be helpful if the notification spooling to a central
+site could selectively be configured on a per-users and/or
+per check-type base.
diff --git a/.bugs/993 b/.bugs/993
new file mode 100644
index 0000000..e5a1de2
--- /dev/null
+++ b/.bugs/993
@@ -0,0 +1,10 @@
+Title: Notification spooling: deliver locally in case of an error
+Component: core
+State: open
+Date: 2013-09-27 11:16:24
+Targetversion: future
+Class: feature
+
+Currently there is a setting "also deliver locally". Nice would be
+a third choice: "also deliver locally in case the central site cannot be reached
+and make this text shorter in the first place."
diff --git a/.bugs/994 b/.bugs/994
new file mode 100644
index 0000000..eab916c
--- /dev/null
+++ b/.bugs/994
@@ -0,0 +1,11 @@
+Title: Notification digest
+Component: core
+State: open
+Date: 2013-09-27 11:17:40
+Targetversion: future
+Class: feature
+
+It would be nice if a user could have a "notification digest"
+instead of one notification per problem. Something like in
+mailinglists. If we implement such a feature, then the digest
+should be on a per-checktype-base.
diff --git a/.bugs/995 b/.bugs/995
new file mode 100644
index 0000000..b6bde05
--- /dev/null
+++ b/.bugs/995
@@ -0,0 +1,11 @@
+Title: EC: owner field is not being used
+Component: ec
+State: open
+Date: 2013-09-27 11:18:36
+Targetversion: future
+Class: nastiness
+
+The EC has a field "owner" for each event. When is this field
+being used? I fear that it isn't used at all. We could use this
+in order to store the name of the last one that has updated
+the event.
Module: check_mk
Branch: master
Commit: 3fe9d64d9cb46eefdbc43bee01bc65ae67a62c23
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=3fe9d64d9cb46e…
Author: Götz Golla <gg(a)mathias-kettner.de>
Date: Fri Sep 27 11:16:40 2013 +0200
new version of apc_symmetra check is now reflected in check man page
---
checkman/apc_symmetra | 63 ++++++++++++++++++++++++++++++++++++++++---------
1 file changed, 52 insertions(+), 11 deletions(-)
diff --git a/checkman/apc_symmetra b/checkman/apc_symmetra
index 6231480..0b83668 100644
--- a/checkman/apc_symmetra
+++ b/checkman/apc_symmetra
@@ -8,16 +8,49 @@ description:
{(2)} the output status, {(3)} the battery capacity, {(4)} the battery
temperature, {(5)} the battery current, {(6)} the output voltage and
{(7)} the output current, {(8)} the remaing run time. The output current and
- remaining run time are not checked against
- a level but just being displayed.
+ remaining run time are not checked against a level but are just displayed.
+
+ The check output includes the calibration status of the UPS. During a
+ calibration the check result in section {(2)} is OK even though the UPS is running
+ on battery.
+ The check reads the date of the last calibration and optionally applies an alternative
+ level for the battery capacity on the day of the calibration. This is because the battery
+ capacity is reduced after calibration and may cause an unwanted critical condition
+ with the standard level. In addition a time span after the day of the calibration
+ can be configured during which the post-calibration phase still persists.
examples:
- # Set the critical levels for all APC checks to:
+ # Set the critical levels for the normal operation mode of all APC checks to:
# - battery capacity at 90% or lower
# - battery temperature to 38C or higher
# - battery current to 10A or higher
# - output voltage to 225V or lower
- apc_default_levels = (90, 38, 10, 225)
+ # old method, unsets the post calibration levels
+ apc_default_levels = ( 90, 38, 10, 225 )
+ # new method
+ apc_default_levels = {
+ "levels": ( 90, 38, 10, 225 )
+ }
+
+ # also set the alternative level for the battery capacity and the delay time span
+ apc_default_levels = {
+ "levels": ( 90, 38, 10, 225 ),
+ "post_calibration_levels": {
+ "altcapacity": 50, # in percent
+ "additional_time_span": 60 # in minutes
+ }
+
+ # checkgroup_parameters syntax
+ # please note that the name of the group is apc_symentra, NOT apc_symmetra !
+ checkgroup_parameters.setdefault('apc_symentra', [])
+
+ checkgroup_parameters['apc_symentra'] += [
+ # All UPS in production get other critical levels
+ ( { "levels": (85, 35, 2, 210) }, ["prod"], ALL_HOSTS ),
+ # All UPS get post calibration level of 50%
+ ( { "post_calibration_levels": { "altcapacity": 50 } }, ["prod"],ALL_HOSTS ),
+ ( { "post_calibration_levels": { "additional_time_span": 60 } }, ["prod"], ALL_HOSTS ),
+ ]
perfdata:
This check outputs five performance values: the battery capacity,
@@ -25,14 +58,22 @@ perfdata:
the output current.
inventory:
- Supported.
+ The inventory process checks if the device has a system description OIDs (.1.3.6.1.2.1.1.2.0)
+ and if the name of this OID is known to the test. If this is true the system is inventorized.
[parameters]
-crit_capacity (int): The battery capacity in percent at and below which a critical state is be triggered
-crit_batt_temp (int): The critical temperature of the battery
-crit_batt_curr (int): The critical battery current in Ampere
-crit_voltage (int): The output voltage at and below which a critical state is triggered.
+parameters(dict): parameters is a dictionary with two keys
+
+ {"levels"}: a tuple of critical levels for battery capacity, temperature, current and output
+ voltage. The numbers are integers.
+
+ {"post_calibration_levels"}: a dictionary of two parameters: {"altcapacity"} is the alternative
+ critical level for the battery capacity in the post-calibration phase in precent. {"additional_time_span"}
+ is a time span the post-calibration phase is extended past the day of the calibration in minutes.
+
+parameters(tuple): The old format of a tuple of 4 values is also still supported, containing what
+ is found in the key {"levels"} in the dictionary.
+
[configuration]
-apc_default_levels (int, int, int, int): The default levels to be used
- for inventorized checks. This variable is preset to {(95, 40, 1, 220)}
+apc_default_levels (dict): This variable is preset to {{ "levels": ( 95, 40, 1, 220 ) }}
Module: check_mk
Branch: master
Commit: ee57f70eb2fbc76c9d097460cb95cd7bb32bb95c
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=ee57f70eb2fbc7…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Fri Sep 27 11:02:03 2013 +0200
LDAP Cache Livetime: use better ValueSpec "Age"
---
web/plugins/wato/check_mk_configuration.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/web/plugins/wato/check_mk_configuration.py b/web/plugins/wato/check_mk_configuration.py
index ec25642..52df834 100644
--- a/web/plugins/wato/check_mk_configuration.py
+++ b/web/plugins/wato/check_mk_configuration.py
@@ -731,7 +731,7 @@ register_configvar(group,
register_configvar(group,
"ldap_cache_livetime",
- Integer(
+ Age(
title = _('LDAP Cache Livetime'),
help = _('This option defines the maximum age for using the cached LDAP data. The time of the '
'last LDAP synchronisation is saved and checked on every request to the multisite '