Module: check_mk
Branch: master
Commit: ed44f95ce0b8bd9c1f53aee7c415eabe45344428
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=ed44f95ce0b8bd…
Author: Andreas <ab(a)mathias-kettner.de>
Date: Thu Jun 14 19:28:27 2018 +0200
updated werk text
Change-Id: Icd4b1490f28051fc1bb14d8d6a5b1454ed095cda
---
.werks/5823 | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/.werks/5823 b/.werks/5823
index 8e08447..3694bfa 100644
--- a/.werks/5823
+++ b/.werks/5823
@@ -16,6 +16,7 @@ Currently these two SLA requirements are implemented
<li>State Percentage: The service state OK/WARN/CRIT/UNKNOWN is lower/higher than x
percent</li>
<li>Outage count: Maximum number of outages with a length of x minutes</li>
</ul>
+
Note: An upcoming SLA requirement will be "Minimum time between outages"
@@ -25,10 +26,12 @@ Before the availability data gets forwarded to the computation plugins
(which ch
<li>further shortened by applying timeperiods, for example "Only check
weekdays"</li>
<li>cut into mulitple timeframes (daily/weekly/monthly), specified by period in the
SLA definition</li>
</ul>
+
Each timeframe is computed separately, so you will get several SLA results, if the
timerange you are interested in spans multiple SLA periods.
+
Configuration
First of all you need to configure a SLA definition. Just like views and reports, SLA
definitions are configured per user,
@@ -37,7 +40,6 @@ so you can setup a SLA and publish it to other users.
SLA definitions are not inherently bound to services.
A SLA definition can be assigned to a service, via the WATO rule <tt>Assign SLA to
service</tt>.
For views, the multisite GUI currently offers two different painters to display SLA
information
-
<ul>
<li>SLA - Service specific: This painter renders SLA definitions, which were
assigned by WATO rule. Therefore, one table
column in a view can display multiple SLA definition types. The timerange, however, is
fixed for all SLAs and can be configured in the painter</li>