[checkmk-commits] 5631 New host/ service painter to display the notification postponement reason of the Microcore

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.