Dear Ladies and Gentlemen,
I am writing to suggest that Nag 2.0 (or later) consider reporting
availability against SLA.
It may be possible to
1 Define SLAPeriods like the current TimePeriod objects. This attribute
is a property of host and service objects.
2 Define an SLAGuarantee for a host or service specifying the lower
bound of the available time that the measured availability must exceed
to meet the guarantee.
(eg SLAGuarantee_999, SLAGuarantee_9999 so that if these are applied to
a service or host the availability of that service or host must be more
than 99.9 and 99.99% respectively for the specified SLA period.
It _may_ be possible for Nagios to calculate availability after each
service check [it does already I think] and submit an alert or
escalation ...
3 Have avail.c discard events that fall outside the SLA period for that
service or host.
4 Have the availability CGI return an extra indication of whether or not
the SLA has been met (if avail >= SLAGuarantee)
Yours sincerely.
--
------------------------------------------------------------------------
Stanley Hopcroft
------------------------------------------------------------------------
'...No man is an island, entire of itself; every man is a piece of the
continent, a part of the main. If a clod be washed away by the sea,
Europe is the less, as well as if a promontory were, as well as if a
manor of thy friend's or of thine own were. Any man's death diminishes
me, because I am involved in mankind; and therefore never send to know
for whom the bell tolls; it tolls for thee...'
from Meditation 17, J Donne.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: Stanley.Hopcroft@IPAustralia.Gov.AU