Module: check_mk
Branch: master
Commit: 33216e7e4261f9805f05b408cdd59e17f2ebbca6
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=33216e7e4261f9…
Author: Sven Panne <sp(a)mathias-kettner.de>
Date: Wed Jan 10 14:14:29 2018 +0100
5477 Rule-based recurring downtimes can have and end now.
Prevously, you could only specify a point in time when a rule-based
recurring downtime starts. You can now optionally specify an additional
point in time when no new downtimes will be started for such a rule, i.e.
effectively disabling that rule from that point onwards.
Note that specifying such an end point is not possible for ad-hoc downtimes,
i.e. the ones entered directly without rules. This is caused by the
underlying Nagios-compatible external commands which don't know such a
field. Simply extending the commands by adding such a field is not a
reliable option: In multi-site environments you can have a mix of monitoring
cores and don't know which site uses which core.
Change-Id: I37a4e2d280da782d42e1b3ebabb1836c1cd70fa4
---
.werks/5477 | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/.werks/5477 b/.werks/5477
new file mode 100644
index 0000000..66c122d
--- /dev/null
+++ b/.werks/5477
@@ -0,0 +1,20 @@
+Title: Rule-based recurring downtimes can have and end now.
+Level: 1
+Component: core
+Compatible: compat
+Edition: cee
+Version: 1.5.0i3
+Date: 1515590636
+Class: feature
+
+Prevously, you could only specify a point in time when a rule-based
+recurring downtime starts. You can now optionally specify an additional
+point in time when no new downtimes will be started for such a rule, i.e.
+effectively disabling that rule from that point onwards.
+
+Note that specifying such an end point is not possible for ad-hoc downtimes,
+i.e. the ones entered directly without rules. This is caused by the
+underlying Nagios-compatible external commands which don't know such a
+field. Simply extending the commands by adding such a field is not a
+reliable option: In multi-site environments you can have a mix of monitoring
+cores and don't know which site uses which core.
Module: check_mk
Branch: master
Commit: 8d30763e98054a4f84cf6963edf6b6e793af9682
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=8d30763e98054a…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Wed Jan 10 14:19:18 2018 +0100
5631 New host/service painter to display the notification postponement reason of the Microcore
The Check_MK Microcore has a mechanic that delays notifications for different reasons. For example
service notifications are delayed when the service is in downtime or when the host of the service
is down.
With the new painters "Notification postponement reason" Check_MK is now showing the reason why
a pending notification for a host/service is not yet sent to the user. This painter has been
added to the host and service detail pages by default.
The users could already check the notification logic and see the current postponement reasons
using the cmc.log, but this needs command line access and is not very comfortable when having a
larger installation which produces a lot of log entries.
Change-Id: I8ab97dabe5d432932a3168baec6470ceabcade59
---
.werks/5631 | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/.werks/5631 b/.werks/5631
new file mode 100644
index 0000000..f3690b5
--- /dev/null
+++ b/.werks/5631
@@ -0,0 +1,20 @@
+Title: New host/service painter to display the notification postponement reason of the Microcore
+Level: 1
+Component: multisite
+Compatible: compat
+Edition: cee
+Version: 1.5.0i3
+Date: 1515590026
+Class: feature
+
+The Check_MK Microcore has a mechanic that delays notifications for different reasons. For example
+service notifications are delayed when the service is in downtime or when the host of the service
+is down.
+
+With the new painters "Notification postponement reason" Check_MK is now showing the reason why
+a pending notification for a host/service is not yet sent to the user. This painter has been
+added to the host and service detail pages by default.
+
+The users could already check the notification logic and see the current postponement reasons
+using the cmc.log, but this needs command line access and is not very comfortable when having a
+larger installation which produces a lot of log entries.
Module: check_mk
Branch: master
Commit: 60434c50d05ddda2c334ad696a2b9ba28e823b3b
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=60434c50d05ddd…
Author: Andreas Umbreit <au(a)mathias-kettner.de>
Date: Fri Jan 5 13:33:48 2018 +0100
5269 cmk-update-agent: New show-config mode
With this werk, a new debugging-feature gets added to the cmk-update-agent(.exe) executable.
You can now display the current configuration and state saved within the cmk-update-agent.cfg and cmk-update-agent.state files.
Please note that the configuration file is prioritized over the state file and only effective configurations will be shown. E.g. a saved Check_MK server from state file will be shadowed by a configured server from cfg file and hence it will not be shown by the show-config mode.
You can invoke the show-config mode by running "cmk-update-agent(.exe) show-config"
Change-Id: I4ee4715a298e824e6c271fc010113ec3a46b721b
---
.werks/5269 | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/.werks/5269 b/.werks/5269
new file mode 100644
index 0000000..0855389
--- /dev/null
+++ b/.werks/5269
@@ -0,0 +1,15 @@
+Title: cmk-update-agent: New show-config mode
+Level: 2
+Component: agents
+Compatible: compat
+Edition: cee
+Version: 1.5.0i3
+Date: 1515154865
+Class: feature
+
+With this werk, a new debugging-feature gets added to the cmk-update-agent(.exe) executable.
+
+You can now display the current configuration and state saved within the cmk-update-agent.cfg and cmk-update-agent.state files.
+Please note that the configuration file is prioritized over the state file and only effective configurations will be shown. E.g. a saved Check_MK server from state file will be shadowed by a configured server from cfg file and hence it will not be shown by the show-config mode.
+
+You can invoke the show-config mode by running "cmk-update-agent(.exe) show-config"