[145317] in North American Network Operators' Group
Re: events
daemon@ATHENA.MIT.EDU (Ben Roeder)
Tue Oct 4 05:58:25 2011
From: Ben Roeder <ben.roeder@sohonet.co.uk>
In-Reply-To: <CAB_zYdJ6au02ofnsVFOw7Zi2hLV+_z4_-uKrkxkCizzsrGq=Xw@mail.gmail.com>
Date: Tue, 4 Oct 2011 10:58:04 +0100
To: harbor235 <harbor235@gmail.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Hi Mike,
We have used octopussy ( http://www.8pussy.org/dokuwiki/doku.php?id=3Dhome=
yes it is work safe :-) ) with ok results.
Have used sec ( simple event correlator =
http://simple-evcorr.sourceforge.net/ ) to some success in simple cases.
Currently having another look at this myself and the following look =
interesting, but have not deployed them yet
http://logstash.net/
http://graylog2.org/about
Ben
On 30 Sep 2011, at 14:50, harbor235 wrote:
> What is everyone using to collect, alert, and analyze syslog data?
> I am looking for something that can generate reports as well as =
support
> multiple vendors. We have done some home grown stuff in the past but
> would be interested in something that incorprates all the best =
features.
>=20
> Soalrwinds, splunk, fwanalog, and others come to mind, any other good =
ones
> out there?
>=20
>=20
> Mike
