Furthermore: would it be possible to validate FQDN from DNS and not from syslog-info hostname. We are getting a lot of weird logfiles as some applications are not including the hostname as the first parameter in the syslog-entries, e.g.: Dec 16 11:47:40 x002 |grep FAILED#012#01212/16/11 09:47:10 [issue_cmd ] STATUS: 1#012#01212/16/11 09:47:10 [issue_cmd ] RESULT:#012#01212/16/11 09:47:10 [issue_cmd ] #012#01212/16/11 09:47:10 [set_host_compat_list] #012#01212/16/11 09:47:10 [issue_cli_cmd ] command is '/opt/vmware/aam/bin/ftcli -domain vmware -cmd "SetUserData HostCompatList text /tmp/hostCompatList"'#012#01212/16/11 09:47:40
Would be nice to validate FQDN from sender DNS query... Thanks in advance :-) ! ~maymann 2012/1/13 Michael Maymann <[email protected]> > Hi List, > > I'm new to rsyslog/syslog in general. > > I would like to syslog from all my 100+ network devices. > Preferably I would like a FQDN.log file for each host (or a FQDN-dir > containing logs from this host if more logfiles per host are best > practice)... > > Can anyone give me an example of (or link to) best practice of this kind > of setup. > > > Thanks in advance :-) ! > > ~maymann > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/
