Yes apologies.  It wasn't clear from what I pasted that it was out of context.  Flo has the syntax correct.

On 3/13/19 11:18 AM, Flo Rance via rsyslog wrote:
You should read the following announcement:
https://www.rsyslog.com/rsyslog-version-numbering-change/

For your parsing error, you're mixing different syntax.

template(name="isilon_tmpl" type="list") {
    property(name="$!modmsg")

    constant(value="\n")

}


Flo

On Wed, Mar 13, 2019 at 4:25 PM Secrist, Eric via rsyslog <
[email protected]> wrote:

Thanks for the response John. I upgraded to version 8.1903.0 from version
8.24. I find it strange that 8.1903 is a more recent version than 8.24.
I attempted to use your approach but ran into parsing config file errors.

Here are the statements that produced the parsing errors:

set $!modmsg = replace($msg,"|",",");
template(name="isilon_tmpl" type="list") {
     string="$!msg\n"
    property(name="$!modmsg")
}

I also tried using the property statement as you described, outside of the
template definition, but that also produced parsing errors.

-----Original Message-----
From: rsyslog <[email protected]> On Behalf Of John
Chivian
Sent: Tuesday, March 12, 2019 12:25 PM
To: [email protected]
Subject: Re: [rsyslog] [External] Re: String replacement

This would be one of those issues where it's best to be at a recent
version.  From experience I can say that both JSON property handling and
the reliability of the replace function are greatly improved since 8.24
which is still the distro default for many.  Here's what I do...

set $!modmsg = replace($msg,"{","");
property(name="$!modmsg")

Regards,



_______________________________________________
rsyslog mailing list
http://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.

Reply via email to