-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 william(at)elan.net wrote: > > On Sun, 18 Mar 2007, virendra rode // wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> william(at)elan.net wrote: >>> >>> >>> On Sun, 18 Mar 2007, Rubens Kuhl Jr. wrote: >>> >>>> What open-source or low-budget tools are operators using for SLA >>>> monitoring when the reports (current state and historical) should be >>>> available to customers ? >>> >>> Please define SLA in terms of monitoring. >> - ----------------------- >> I would say, >> >> - - availability > > OK - network connection up or UP/DOWN with list of when its down > and for how long and SLA based on amount of time its been down > or more commonly time_up/time_down*100 > >> - - response time / latency > > ok ping latency graph for user view with SLA based on maximum > average latency over given time period > >> - - utilization > > How is that part of SLA? Or do you mean you gurantee that > your own upstream network connection would not be overutilized? - ----------------- When an object exceeds a specified threshold (e.g. cpu, interface, temperature, routing table, etc) which could cause it to be unavailable triggering an event.
> >> - - accuracy and errors > > accuracy of what? what type of errors, packet drops? - -------------- availability and reachability because we care about of uptime, correct? > >> - - five nines, six nines , take your pick and define your own holy >> grail. > > $ echo "60*24*365*(1-0.99999)" | bc -l > 5.25600 > > You wish to tell me you guarantee network connection to customer to > be down for no more then 5 minutes during the year? Yeh, right :) > (but don't let me discourage any of you in trying to achieve it!) regards, /virendra -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF/rTYpbZvCIJx1bcRAh5vAJ91QWFjQ19jPrB/uzd+eZ8GSztvQACfV4vq LOT5Mf8E/1jG729NrgY8QKw= =zIg8 -----END PGP SIGNATURE-----