Yes, there's. It would be great if you could show us how you send your output to the log consumer today, it would be easier to suggest solutions based on that. On Mon, Nov 7, 2022, 12:09 Maurya, Shivani <shivani.maurya@intel.com> wrote:
Hi All,
With the older Syslog-ng RFC format (*rfc 3164*), the devices used to send the syslog messages in the below format –
%TAG TIMESTAMP FULLHOSTFROM SEVERITY MSG
*Example -* %SYSMGR-2-NON_VOLATILE_DB_INODE_FULL:2022 Nov 7 03:54:30 MST: SYSMGR-2-NON_VOLATILE_DB_INODE_FULL: System non-volatile inode storage usage is unexpectedly high at 96
But with the new syslog-ng RFC format (*rfc 5425*), the devices send the syslog messages in below format –
TIMESTAMP FULLHOSTFROM SEVERITY MSG
Is there a way to update/format the messages (rfc 5424) to be pre-fixed with %TAG ?
Regards,
Shivani Maurya
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq