[95418] in North American Network Operators' Group
Re: SLA monitoring and reporting to customers
daemon@ATHENA.MIT.EDU (virendra rode //)
Mon Mar 19 00:31:52 2007
Date: Sun, 18 Mar 2007 21:30:29 -0700
From: virendra rode // <virendra.rode@gmail.com>
Reply-To: virendra.rode@gmail.com
To: Ray Burkholder <ray@oneunified.net>
Cc: 'NANOG list' <nanog@nanog.org>
In-Reply-To: <006b01c769bc$71157bf0$0202fea9@oneunified.local>
Errors-To: owner-nanog@merit.edu
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ray Burkholder 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 ?
>>
>
> Here is one way to do it on the cheap.
>
> I have worked with Cricket and genDevConfig extensively. genDevConfig will
> scan a router and automatically create the cricket SNMP commands to pull the
> IP SLA statistics out, or what ever other statistics in which you are
> interested. This scanning parameters are stored in a cricket config file
> and the data in rrd files.
>
> A custom Perl script, with or without some Mason templating could be used
> along with a connection to a backend Postgresql database for user
> authentication.
>
> It should be relatively easy to create two tables:
> a) userid, username or email, password
> b) userid, router, interface/id for sla
>
> Then that data can be used in a Perl script to generate a page of customer
> specific graphs in a user-authenticated web site.
>
> Ray.
- ------------------------
Generally if you are responsible for meeting a SLA, one has to take
outages into account.
regards,
/virendra
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF/hHlpbZvCIJx1bcRAgYxAKC14AbDi47oVrMkE73XgUpY+PTBPgCfQiNZ
OW5X3VjTPh71qtcq38ou8cM=
=imML
-----END PGP SIGNATURE-----
