test tool: split/forward syslog from production old-syslogd to syslog-ng?
I'm trying to figure out how to configure/test a new syslog-ng system without disrupting my current old-style syslogd on a Solaris central logserver. The challenges are: preserving level/facility and perserving the originating host IP/name; thus a simple "*.debug @newserver" doesn't work. I *think* I can come up with a perl script to take nc (netcat) -l -v output, re-write the messages to contain the original hostname, and use netcat again to forward it off to the new server under development. e.g.: > sudo ./nc -l -u -p 514 -v listening on [any] 514 ... connect to [172.19.248.122] from eponymous.lab.netapp.com [172.19.248.40] 3357 <0>foofdsasdfasdf and rewrite that to <0>${timedate} 172.19.248.40 foofdsasdfasdf and ship it off. But I was wondering if anyone had already built such a tool....?
2004-02-11, sze keltezéssel 21:04-kor David Carmean ezt írta:
I'm trying to figure out how to configure/test a new syslog-ng system without disrupting my current old-style syslogd on a Solaris central logserver.
The challenges are: preserving level/facility and perserving the originating host IP/name; thus a simple "*.debug @newserver" doesn't work.
if you turn keep_hostname(on) on your syslog-ng server, the hostname part will not be changed. the level/facility information is never changed in any case. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
participants (2)
-
Balazs Scheidler
-
David Carmean