I had always thought that $MESSAGE also contained a header with host and timestamp information. If you're saying that isn't so, then we must be getting the date included as part of the message from the originating host. What I'm seeing below, along with the fact that I'm now seeing that some of the log files have the double date and some do not, seems to support that conclusion. We simply are trying to get a message to look like this: $ISODATE $HOST $MESSAGE Looks like we may need to rewrite the messages to get them into a consistent format? # Source source pan_splunk_udp { network(port(514) so-reuseport(1) so-rcvbuf(268435456) transport("udp") flags(syslog-protocol) log-fetch-limit(256000) persist-name('udp1') ); network(port(514) so-reuseport(1) so-rcvbuf(268435456) transport("udp") flags(syslog-protocol) log-fetch-limit(256000) persist-name('udp2') ); network(port(514) so-reuseport(1) so-rcvbuf(268435456) transport("udp") flags(syslog-protocol) log-fetch-limit(256000) persist-name('udp3') ); network(port(514) so-reuseport(1) so-rcvbuf(268435456) transport("udp") flags(syslog-protocol) log-fetch-limit(256000) persist-name('udp4') ); }; # Destination destination d_file { file("`BASEPATH`/$location/$HOST/$app/${HOST}_$app.log" create_dirs(yes) dir-owner("root") dir-group("root") dir-perm(0700) owner("root") group("root") perm(0640) flags("threaded", "no-multi-line") template("${S_ISODATE} ${MESSAGE}\n")); }; If I remove the template from the destination above, everything works fine. The date and host is written on each line, however, the date is not in the format we would like since it does not include the year. ... if { # app=ise filter { message('-ise-'); }; rewrite { set("ise" value("app")); }; destination(d_file_no_location); }... I'm having trouble finding a line that has the double date anywhere but in the Cisco ISE logs. It may only be affecting those logs. I think it's pretty clear now that the second date is part of the log message as it is sent by the client. 2020-08-25T15:34:44+00:00 Tue Mar 10 12:54:23 PDT 2020 by xxxxx, cisco-av-pair=lldp-tlv=lldpSystemName=XXX, cisco-av-pair= lldp-tlv=lldpSystemCapabilitiesMap=00:04:00:04, cisco-av-pair=lldp-tlv=lldpTimeToLive=00:78, cisco-av-pair=lldp-tlv=lldpPortId=01:30, cisco-av... -Mark -----Original Message----- From: syslog-ng <syslog-ng-bounces@lists.balabit.hu> On Behalf Of Peter Kokai (pkokai) Sent: Wednesday, August 26, 2020 11:15 To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Subject: [EXTERNAL] Re: [syslog-ng] Message Macros Hello, The ${MESSAGE} macro is not supposed to hold dates. If that macro holds a date that is like a parsing issue, or you simply useing flags(no-parse) flags in that source. Would you mind sharing a configuration and input that produces double date in your case ? Also if you have the possibility to turn on debug logs (probably not production) -Fedvt option can be helpful as it is going to print exactly what value the MESSAGE macro is assigned. Example of such log: ``` [2020-08-26T18:13:38.652356] Setting value; name='MESSAGE', value='-- Generated message. --', msg='0x616000008780' ``` -- Kokan On Wed, Aug 26, 2020 at 02:52:46PM +0000, Faine, Mark R. (MSFC-IS40)[NICS] wrote:

CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.

Is it possible to break up the $MESSAGE macro into smaller macros that constitute the entire message? The reason I ask is that we tried this format in our destination:

template("${S_ISODATE} ${MESSAGE}\n")

However, we get two dates now, since I'm assuming one is part of the $MESSAGE macro, and we also lost the $HOST in our messages.

We just want the output to be exactly like it would be without specifying a template but with an ISO date, followed by the hostname/ip, and the rest of the message excluding the date.

Thanks, -Mark

______________________________________________________________________________ Member info: https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protect... Documentation: https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protect... FAQ: https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protect...

______________________________________________________________________________ Member info: https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.balabit.hu_mailma... Documentation: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.balabit.com_support_... FAQ: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.balabit.com_wiki_sys...