From: Mark Shields <laebshade@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Sysloggers
Date: Wed, 17 Jun 2009 10:33:39 -0400 [thread overview]
Message-ID: <642958cc0906170733o3e83e4a3v58c9c38652ff905b@mail.gmail.com> (raw)
In-Reply-To: <200906162249.01707.alan.mckinnon@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
On Tue, Jun 16, 2009 at 4:49 PM, Alan McKinnon <alan.mckinnon@gmail.com>wrote:
> Hi,
>
> Does anyone have decent experience with sysloggers other than syslog-ng,
> and
> be willing to share experiences?
>
> I'm especially interested in some of the advanced features of syslog-ng
> Premium from Balabit.com (based on and extending their open source
> version):
>
> SSL-encrypted traffic over the network
> Disk-based buffering on the client
> Windows agents
> Timezone aware (which syslog doesn't do and syslog-ng only partially)
> Encrypted disk files
> Filter, parse and rewrite incoming logs (vital if you need the auth log
> over
> here and the password field stored over there, without jumping through
> hoops
> first)
> High scalability - 2000 Cisco devices and 200+ servers to start,
> distributed
> country wide
>
> --
> alan dot mckinnon at gmail dot com
>
>
syslog-ng is the de facto standard. Metalog is fine for desktops, but I use
syslog-ng on all my servers. Nearly all programs that can process log files
are compatible with it.
--
- Mark Shields
[-- Attachment #2: Type: text/html, Size: 1420 bytes --]
next prev parent reply other threads:[~2009-06-17 14:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 20:49 [gentoo-user] Sysloggers Alan McKinnon
2009-06-17 14:33 ` Mark Shields [this message]
2009-06-17 18:35 ` Dale
2009-06-17 21:31 ` Alan McKinnon
2009-06-17 21:48 ` Neil Bothwick
2009-06-17 22:17 ` Alan McKinnon
2009-06-17 22:37 ` Mick
2009-06-19 14:11 ` [gentoo-user] Sysloggers Harry Putnam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=642958cc0906170733o3e83e4a3v58c9c38652ff905b@mail.gmail.com \
--to=laebshade@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox