[194353] in North American Network Operators' Group
Re: SLA Monitoring
daemon@ATHENA.MIT.EDU (Alan Kemp)
Wed Apr 12 22:55:22 2017
X-Original-To: nanog@nanog.org
From: Alan Kemp <alan@irisns.com>
Date: Wed, 12 Apr 2017 15:40:28 +0200
To: nanog@nanog.org
In-Reply-To: <b85b8d22-ec6a-93ae-7333-878d6178b509@unlimitednet.us>
Errors-To: nanog-bounces@nanog.org
Hi Mike,
We have customers that use Cisco IPSLA or juniper RPM to the actual SLA =
test, then use an NMS system to collect and report on that data.
So I suppose depending on what you mean by monitoring there are a few =
options.
1. Real time graphing collected via SNMP
2. Proactive alerting based on threshold configuration
3. Reporting on SLA based on contractual obligations.
4. Central provisioning of the individual tests.
I=E2=80=99m a little biased as I work for a monitoring company, but if =
you let me know what you mean by monitoring I can try help out.
regards
Alan=20
> On 12 Apr 2017, at 2:35 PM, Jason Canady <jason@unlimitednet.us> =
wrote:
>=20
> We use various tools for monitoring here. Pingdom for external =
monitoring, Observium for internal and SmokePing for internal/external.
>=20
> As far as Pingdom goes, we ended up paying for 3 years to lock in =
pricing because it keeps going up and the service doesn't improve, but =
it is useful. I need to find an alternative prior to the next renewal.
>=20
> --=20
>=20
> Jason Canady
> Unlimited Net, LLC
> Responsive, Reliable, Secure
>=20
> On 4/11/17 6:57 PM, Mike Hammett wrote:
>> What do you guys use for monitoring of SLAs, be it an upstream or a =
downstream SLA? I know of a couple services, just looking to see who's =
doing what and how they like it.
>>=20
>>=20
>>=20
>>=20
>> -----
>> Mike Hammett
>> Intelligent Computing Solutions
>> http://www.ics-il.com
>>=20
>> Midwest-IX
>> http://www.midwest-ix.com
>=20
--
Alan Kemp
Support: 0861 IRISNS (474767) or +27 21140 IRIS (4747)
Mobile: +27 83 257 5970
IRIS Network Systems
