[checkmk-commits] Improved wording a bit. Fixed a few typos.

Module: check_mk Branch: master Commit: 619fcb9e31b24ca044ba6664477a4299d5343801 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=619fcb9e31b24c… Author: Sven Panne &lt;sp(a)mathias-kettner.de&gt; Date: Mon Apr 23 14:26:57 2018 +0200 Improved wording a bit. Fixed a few typos. Change-Id: I9aef5740f2a99088aa0ca9bca3d49f2580485d3e --- .werks/4989 | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/.werks/4989 b/.werks/4989 index cdc5df9..07d5839 100644 --- a/.werks/4989 +++ b/.werks/4989 @@ -8,27 +8,27 @@ Date: 1499935734 Class: feature The Event Console is now saving whether or not a host that can be found in the core -was in downtime or not. Based on this information the event handling can be influenced +was in downtime or not. Based on this information, the event handling can be influenced in different ways. -The idea is: In the moment a host is in downtime all events generated by the host are -"handled problems". The events should be created and be visible during the downtime to -assist during maintenance. After maintenance the events that have been created in the -downtime are not interesting anymore. +The idea is: In the moment a host is in downtime, all events generated by the +host are "handled problems". The events are still created, and they are visible +during the downtime to assist maintenance. After the maintenance, the events +that have been created during the downtime are not interesting anymore. What has changed: <ul> -<li>Each event has a new attribute <tt>event_host_in_downtime</tt>. Assuming <i>0</i> +<li>Each event has a new attribute <tt>event_host_in_downtime</tt>, assuming <i>0</i> (no) for existing events.</li> -<li>It is possible to filter event views by this information</li> -<li>Separate counting events are created for in downtime / not in downtime</li> -<li>Events are added during downtime and visible in the default events views<li> -<li>The tactical overview does not count events created in host downtime in the -"handled problems" column</li> -<li>Events created during downtime will be archived automatically after the host -left the downtime</li> -<li>Actions are handled independent of the downtime by default. But you have the +<li>It is possible to use this information in event view filters.</li> +<li>Separate counting events are created for "in downtime" / "not in downtime".</li> +<li>Events are added during downtime, and they are visible in the default events views.</li> +<li>The tactical overview does not count events created during a host downtime in the +"Unhandled" column.</li> +<li>Events created during a host downtime will be archived automatically after the host +left the downtime.</li> +<li>Actions are handled independently of the host downtime by default, but you have the option to only execute actions when the host was not in downtime</li> </ul>