I have a central logger (several of them) setup where multiple servers are forwarding logs and am receiving unintelligible log names on the collector.
It appears the name of each file is parsed incorrectly. Here is an example: -rw------- 1 root root 151 Feb 1 11:00 x64;.log -rw------- 1 root root 104 Feb 1 11:00 utions.com_10514].log -rw------- 1 root root 458 Feb 1 11:16 _ID="_d7b4a97eccdad22d3f8e69f01a28a9553bf97ef83e".log -rw------- 1 root root 710 Feb 1 11:16 REASON="N.log -rw------- 1 root root 384 Feb 1 11:17 com".log -rw------- 1 root root 1382 Feb 1 11:17 ONID=_d7b4a97eccdad22d3f8e69f01a28a9553bf97ef83e.log Can anyone provide some guidance on how I clean up these names and make them useful? thanks, *Scott Slattery* -- *For more information on how and why we collect your personal information, please visit our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement>.* _______________________________________________ rsyslog mailing list https://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
