Setting and using variables
Is there a way to set variables in syslog-ng? I have a log path with about 20 if/else branches and each one does a unnamed destination for that branch: log { source(pan_splunk); if ( tags('mytag') ) { destination { file("/var/log/remote/backup/$HOST/asa/${HOST}_asa.log" create-dirs(yes) dir-owner("splunk") dir-group("splunk") dir-perm(0750)); }; } elif ( message('something else') ) { destination { file("/var/log/remote/backup/$HOST/pubfw/${HOST}_pubfw.log" create-dirs(yes) dir-owner("splunk") dir-group("splunk") dir-perm(0750)); }; } elif { filter { message('foo') or message('bar') or message('baz') or ... I'd need to introduce another directory level as a variable and I'd also like to change an existing part of the path to a variable so that then I could then do something like this: if ( tags('mytag') ) { app = asa location = msfc elif ... and at the end I could then just do a single destination that had a file path with the variables file("/var/log/remote/backup/$location/$HOST/$app/${HOST}_$app.log" Thanks, -Mark
Hello, You could use *rewrite* rule to add nv-pair to each message: log { source(s_local); if (message('a')) { rewrite { set("foo" value("app")); set("bar" value("location")); }; } elif (message('b')) { rewrite { set("foob" value("app")); set("barb" value("location")); }; } else { rewrite { set("default" value("app")); set("default" value("location")); }; }; destination { file("/dev/stdout" template("$app $location\n")); }; }; Something like this. -- Kokan On Fri, Mar 22, 2019 at 2:37 PM Faine, Mark R. (MSFC-IS40)[NICS] < mark.faine@nasa.gov> wrote:
Is there a way to set variables in syslog-ng?
I have a log path with about 20 if/else branches and each one does a unnamed destination for that branch:
log { source(pan_splunk); if ( tags('mytag') ) { destination { file("/var/log/remote/backup/$HOST/asa/${HOST}_asa.log" create-dirs(yes) dir-owner("splunk") dir-group("splunk") dir-perm(0750)); }; } elif ( message('something else') ) { destination { file("/var/log/remote/backup/$HOST/pubfw/${HOST}_pubfw.log" create-dirs(yes) dir-owner("splunk") dir-group("splunk") dir-perm(0750)); }; } elif { filter { message('foo') or message('bar') or message('baz') or ...
I'd need to introduce another directory level as a variable and I'd also like to change an existing part of the path to a variable so that then I could then do something like this:
if ( tags('mytag') ) { app = asa location = msfc elif ...
and at the end I could then just do a single destination that had a file path with the variables file("/var/log/remote/backup/$location/$HOST/$app/${HOST}_$app.log"
Thanks, -Mark
______________________________________________________________________________ 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
Thank you both, this is very helpful. I can use this. Is it only possible to set variables by adding to the message? Can variables exist outside of the message? -Mark From: syslog-ng <syslog-ng-bounces@lists.balabit.hu> On Behalf Of Péter, Kókai Sent: Saturday, March 23, 2019 4:34 AM To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Subject: Re: [syslog-ng] Setting and using variables Hello, You could use *rewrite* rule to add nv-pair to each message: log { source(s_local); if (message('a')) { rewrite { set("foo" value("app")); set("bar" value("location")); }; } elif (message('b')) { rewrite { set("foob" value("app")); set("barb" value("location")); }; } else { rewrite { set("default" value("app")); set("default" value("location")); }; }; destination { file("/dev/stdout" template("$app $location\n")); }; }; Something like this. -- Kokan On Fri, Mar 22, 2019 at 2:37 PM Faine, Mark R. (MSFC-IS40)[NICS] <mark.faine@nasa.gov<mailto:mark.faine@nasa.gov>> wrote: Is there a way to set variables in syslog-ng? I have a log path with about 20 if/else branches and each one does a unnamed destination for that branch: log { source(pan_splunk); if ( tags('mytag') ) { destination { file("/var/log/remote/backup/$HOST/asa/${HOST}_asa.log" create-dirs(yes) dir-owner("splunk") dir-group("splunk") dir-perm(0750)); }; } elif ( message('something else') ) { destination { file("/var/log/remote/backup/$HOST/pubfw/${HOST}_pubfw.log" create-dirs(yes) dir-owner("splunk") dir-group("splunk") dir-perm(0750)); }; } elif { filter { message('foo') or message('bar') or message('baz') or ... I'd need to introduce another directory level as a variable and I'd also like to change an existing part of the path to a variable so that then I could then do something like this: if ( tags('mytag') ) { app = asa location = msfc elif ... and at the end I could then just do a single destination that had a file path with the variables file("/var/log/remote/backup/$location/$HOST/$app/${HOST}_$app.log" Thanks, -Mark ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.balabit.hu_mailman_listinfo_syslog-2Dng&d=DwMFaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=zMyZvtxRXMBKZZYKVMke9zplWK320p3d51BzuU4jwWo&m=0oCgkJqh7N_Ja-VdtmDlAS5pzhA0puqJm8zcAaXJyjY&s=YY8TzLxmhOq_o7pu7ONHbV6I7OVpIy1P7TQUfp_hm8M&e=> Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.balabit.com_support_documentation_-3Fproduct-3Dsyslog-2Dng&d=DwMFaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=zMyZvtxRXMBKZZYKVMke9zplWK320p3d51BzuU4jwWo&m=0oCgkJqh7N_Ja-VdtmDlAS5pzhA0puqJm8zcAaXJyjY&s=DrlT7sUf5X_xKiPK3ca7WDhiw-xr4D7mtnSfL2yXiAQ&e=> FAQ: http://www.balabit.com/wiki/syslog-ng-faq<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.balabit.com_wiki_syslog-2Dng-2Dfaq&d=DwMFaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=zMyZvtxRXMBKZZYKVMke9zplWK320p3d51BzuU4jwWo&m=0oCgkJqh7N_Ja-VdtmDlAS5pzhA0puqJm8zcAaXJyjY&s=LvSPfbLLubjWgsCznHSgC7oIi6YzCi5LjVylqe_y5f8&e=>
On Mon, Mar 25, 2019 at 01:07:17PM +0000, Faine, Mark R. (MSFC-IS40)[NICS] wrote:
Thank you both, this is very helpful. I can use this. Is it only possible to set variables by adding to the message? Can variables exist outside of the message?
The whole message routing logic is message-scoped, so variables are attached to a message. You can set global variables using 'define' directives.
I see. That actually clears up a lot of questions. I did see the global variables option and was thinking about using it for part of my path in the template. From what I've read environment variables are available as global variables. Part of my path should only exist if running on a backup (secondary) server. On the primary servers I have: /var/log/remote and the backups have: /var/log/remote/backup I was thinking that I could determine which server we are on in root's .bashrc or in the startup script for syslog-ng and set an environment variable, and then in the template, I could use the variable: template log_path { template("`BASEPATH`/$location/$HOST/$app/${HOST}_$app.log"); }; Do you think that would work? Thanks, -Mark -----Original Message----- From: syslog-ng <syslog-ng-bounces@lists.balabit.hu> On Behalf Of Fabien Wernli Sent: Monday, March 25, 2019 8:24 AM To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Subject: Re: [syslog-ng] Setting and using variables On Mon, Mar 25, 2019 at 01:07:17PM +0000, Faine, Mark R. (MSFC-IS40)[NICS] wrote:
Thank you both, this is very helpful. I can use this. Is it only possible to set variables by adding to the message? Can variables exist outside of the message?
The whole message routing logic is message-scoped, so variables are attached to a message. You can set global variables using 'define' directives. ______________________________________________________________________________ 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...
Hello, In short: only messages can have *variables*. Approach #1 Let's imagine that for example a *logpath* can have variable. Create the following construct: log { var("location", "space"); var("app", "sputnik-1"); }; Also do it in a way that those variables scope and lifetime are limited to the that *logpath*. (Which is just an arbitrary choose, but also somehow makes sense at first glance.) Your configuration would be as follows: log { source(s_local); if (message('a')) { var("app", "foo"); var("location" "bar"); } elif (message('b')) { var("app", "foob"); var("location" "barb"); } else { var("app", "default"); var("location" "default"); }; destination { file("/dev/stdout" template("$app $location\n")); }; }; The *if-else* actually just a *logpath* in the background - can be rewritten so it became a *log*, so our scope would still apply. When the message reaches the *destination* it cannot see the *variable* as neither its lifetime and scope allows it. This approach won't solve this issue. Approach #2 The same as above but let's patch the lifetime/scope issue. Let's increase both of them to be available from parent (global can be done, but won't change much). log { log { var("location", "space"); var("app", "sputnik-1"); }; #location works here }; #but not here In this case the variable collide with each other, there is no useful merge strategy (imho).
From this it seems that even if *logpath* could have variable support, it would not solve your issue. At least I do not see a proper way to do it on paper.
Also I think from the above it feels like it is actually a property of the message nor the pipeline it traverse. If you have an idea that solves the above issue I would be happy to hear it. -- Kokan On Mon, Mar 25, 2019 at 2:07 PM Faine, Mark R. (MSFC-IS40)[NICS] < mark.faine@nasa.gov> wrote:
Thank you both, this is very helpful. I can use this. Is it only possible to set variables by adding to the message? Can variables exist outside of the message?
-Mark
*From:* syslog-ng <syslog-ng-bounces@lists.balabit.hu> *On Behalf Of *Péter, Kókai *Sent:* Saturday, March 23, 2019 4:34 AM *To:* Syslog-ng users' and developers' mailing list < syslog-ng@lists.balabit.hu> *Subject:* Re: [syslog-ng] Setting and using variables
Hello,
You could use *rewrite* rule to add nv-pair to each message:
log {
source(s_local);
if (message('a')) {
rewrite {
set("foo" value("app"));
set("bar" value("location"));
};
}
elif (message('b')) {
rewrite {
set("foob" value("app"));
set("barb" value("location"));
};
}
else {
rewrite {
set("default" value("app"));
set("default" value("location"));
};
};
destination {
file("/dev/stdout" template("$app $location\n"));
};
};
Something like this.
--
Kokan
On Fri, Mar 22, 2019 at 2:37 PM Faine, Mark R. (MSFC-IS40)[NICS] < mark.faine@nasa.gov> wrote:
Is there a way to set variables in syslog-ng?
I have a log path with about 20 if/else branches and each one does a unnamed destination for that branch:
log { source(pan_splunk); if ( tags('mytag') ) { destination { file("/var/log/remote/backup/$HOST/asa/${HOST}_asa.log" create-dirs(yes) dir-owner("splunk") dir-group("splunk") dir-perm(0750)); }; } elif ( message('something else') ) { destination { file("/var/log/remote/backup/$HOST/pubfw/${HOST}_pubfw.log" create-dirs(yes) dir-owner("splunk") dir-group("splunk") dir-perm(0750)); }; } elif { filter { message('foo') or message('bar') or message('baz') or ...
I'd need to introduce another directory level as a variable and I'd also like to change an existing part of the path to a variable so that then I could then do something like this:
if ( tags('mytag') ) { app = asa location = msfc elif ...
and at the end I could then just do a single destination that had a file path with the variables file("/var/log/remote/backup/$location/$HOST/$app/${HOST}_$app.log"
Thanks, -Mark
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.balabit.hu_mailman_listinfo_syslog-2Dng&d=DwMFaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=zMyZvtxRXMBKZZYKVMke9zplWK320p3d51BzuU4jwWo&m=0oCgkJqh7N_Ja-VdtmDlAS5pzhA0puqJm8zcAaXJyjY&s=YY8TzLxmhOq_o7pu7ONHbV6I7OVpIy1P7TQUfp_hm8M&e=> Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.balabit.com_support_documentation_-3Fproduct-3Dsyslog-2Dng&d=DwMFaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=zMyZvtxRXMBKZZYKVMke9zplWK320p3d51BzuU4jwWo&m=0oCgkJqh7N_Ja-VdtmDlAS5pzhA0puqJm8zcAaXJyjY&s=DrlT7sUf5X_xKiPK3ca7WDhiw-xr4D7mtnSfL2yXiAQ&e=> FAQ: http://www.balabit.com/wiki/syslog-ng-faq <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.balabit.com_wiki_syslog-2Dng-2Dfaq&d=DwMFaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=zMyZvtxRXMBKZZYKVMke9zplWK320p3d51BzuU4jwWo&m=0oCgkJqh7N_Ja-VdtmDlAS5pzhA0puqJm8zcAaXJyjY&s=LvSPfbLLubjWgsCznHSgC7oIi6YzCi5LjVylqe_y5f8&e=>
______________________________________________________________________________ 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
I’m looking through the documentation at templates, macros, and destinations. Every example I see is something like yours where it is destination { file("<path>" "<template>")); }; What I'd like to do is something more like: A single template: template log_path { template("/var/log/remote/backup/$location/$HOST/$app/${HOST}_$app.log"); }; A single destination: destination d_file { file(template(log_path)); }; Then in my if/else do as you have demonstrated: rewrite { set("foo" value("app")); set("bar" value("location")); }; With the result being that all the files use the same destination which uses the same template. Is this possible? The examples I've seen so far would seem to suggest that it wouldn't. Thanks, -Mark From: syslog-ng <syslog-ng-bounces@lists.balabit.hu> On Behalf Of Péter, Kókai Sent: Saturday, March 23, 2019 4:34 AM To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Subject: Re: [syslog-ng] Setting and using variables Hello, You could use *rewrite* rule to add nv-pair to each message: log { source(s_local); if (message('a')) { rewrite { set("foo" value("app")); set("bar" value("location")); }; } elif (message('b')) { rewrite { set("foob" value("app")); set("barb" value("location")); }; } else { rewrite { set("default" value("app")); set("default" value("location")); }; }; destination { file("/dev/stdout" template("$app $location\n")); }; }; Something like this. -- Kokan On Fri, Mar 22, 2019 at 2:37 PM Faine, Mark R. (MSFC-IS40)[NICS] <mailto:mark.faine@nasa.gov> wrote: Is there a way to set variables in syslog-ng? I have a log path with about 20 if/else branches and each one does a unnamed destination for that branch: log { source(pan_splunk); if ( tags('mytag') ) { destination { file("/var/log/remote/backup/$HOST/asa/${HOST}_asa.log" create-dirs(yes) dir-owner("splunk") dir-group("splunk") dir-perm(0750)); }; } elif ( message('something else') ) { destination { file("/var/log/remote/backup/$HOST/pubfw/${HOST}_pubfw.log" create-dirs(yes) dir-owner("splunk") dir-group("splunk") dir-perm(0750)); }; } elif { filter { message('foo') or message('bar') or message('baz') or ... I'd need to introduce another directory level as a variable and I'd also like to change an existing part of the path to a variable so that then I could then do something like this: if ( tags('mytag') ) { app = asa location = msfc elif ... and at the end I could then just do a single destination that had a file path with the variables file("/var/log/remote/backup/$location/$HOST/$app/${HOST}_$app.log" Thanks, -Mark ______________________________________________________________________________ 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...
I think you're misunderstanding the template concept. A template is there to tell syslog-ng in what format each message will be written to the destination. I might be misunderstanding, but if you want the same template, different files but only one destination, this could be what you want: template my_template { template("$DATE $HOST $PROGRAM $MESSAGE\n"); }; destination d_file { file( "/var/log/remote/backup/$location/$HOST/$app/${HOST}_$app.log" template(my_template) ); };
Thanks, yes, I eventually figured that out, but that means that template is not needed. I don't need to change the format of the message only the destination path. I don't know if I can do file attachments here so I'll summarize: (I've sanitized and stripped out lines to make it shorter) destination d_file { file("/var/log/remote/backup/$location/$HOST/$app/${HOST}_$app.log") create-dirs(yes) dir-owner("splunk") dir-group("splunk") dir-perm(0750)); ); In addition, I have a path that throws out some messages: log { source(pan_splunk); if {... destination { file("/dev/null"); }; }; }; I then have a log path that first sets the location variable in the message: if ( message('afrc') then { rewrite { set("afrc" value("location")); }; } elif ... ... } else { rewrite { set("unknown" value("location")); }; }; Then it sets the app variable: if ( tags('ASA-') ) { rewrite { set("asa" value("app")); }; } elif ... } else { rewrite { set("misc" value("app")); }; }; Then I set the destination to the file destination: destination(d_file); Mark Faine System Administrator SAIC/NICS 215 Wynn Dr. 5065 Huntsville, AL 35805 256-961-1295 (Desk) 256-617-4861 (Work Cell) -----Original Message----- From: syslog-ng <syslog-ng-bounces@lists.balabit.hu> On Behalf Of Fabien Wernli Sent: Monday, March 25, 2019 9:24 AM To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Subject: Re: [syslog-ng] Setting and using variables I think you're misunderstanding the template concept. A template is there to tell syslog-ng in what format each message will be written to the destination. I might be misunderstanding, but if you want the same template, different files but only one destination, this could be what you want: template my_template { template("$DATE $HOST $PROGRAM $MESSAGE\n"); }; destination d_file { file( "/var/log/remote/backup/$location/$HOST/$app/${HOST}_$app.log" template(my_template) ); }; ______________________________________________________________________________ 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...
Forgive my use of "then", I'm used to an 'if' having a 'then'. :) I've corrected it and I'm getting a clean syntax check. About to test it now. Thanks, -Mark Mark Faine System Administrator SAIC/NICS 215 Wynn Dr. 5065 Huntsville, AL 35805 256-961-1295 (Desk) 256-617-4861 (Work Cell) -----Original Message----- From: syslog-ng <syslog-ng-bounces@lists.balabit.hu> On Behalf Of Faine, Mark R. (MSFC-IS40)[NICS] Sent: Monday, March 25, 2019 10:04 AM To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Subject: [non-nasa source] Re: [syslog-ng] Setting and using variables Thanks, yes, I eventually figured that out, but that means that template is not needed. I don't need to change the format of the message only the destination path. I don't know if I can do file attachments here so I'll summarize: (I've sanitized and stripped out lines to make it shorter) destination d_file { file("/var/log/remote/backup/$location/$HOST/$app/${HOST}_$app.log") create-dirs(yes) dir-owner("splunk") dir-group("splunk") dir-perm(0750)); ); In addition, I have a path that throws out some messages: log { source(pan_splunk); if {... destination { file("/dev/null"); }; }; }; I then have a log path that first sets the location variable in the message: if ( message('afrc') then { rewrite { set("afrc" value("location")); }; } elif ... ... } else { rewrite { set("unknown" value("location")); }; }; Then it sets the app variable: if ( tags('ASA-') ) { rewrite { set("asa" value("app")); }; } elif ... } else { rewrite { set("misc" value("app")); }; }; Then I set the destination to the file destination: destination(d_file); Mark Faine System Administrator SAIC/NICS 215 Wynn Dr. 5065 Huntsville, AL 35805 256-961-1295 (Desk) 256-617-4861 (Work Cell) -----Original Message----- From: syslog-ng <syslog-ng-bounces@lists.balabit.hu> On Behalf Of Fabien Wernli Sent: Monday, March 25, 2019 9:24 AM To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Subject: Re: [syslog-ng] Setting and using variables I think you're misunderstanding the template concept. A template is there to tell syslog-ng in what format each message will be written to the destination. I might be misunderstanding, but if you want the same template, different files but only one destination, this could be what you want: template my_template { template("$DATE $HOST $PROGRAM $MESSAGE\n"); }; destination d_file { file( "/var/log/remote/backup/$location/$HOST/$app/${HOST}_$app.log" template(my_template) ); }; ______________________________________________________________________________ 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... ______________________________________________________________________________ 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...
Hi Mark, On Fri, Mar 22, 2019 at 01:37:29PM +0000, Faine, Mark R. (MSFC-IS40)[NICS] wrote:
Is there a way to set variables in syslog-ng?
You can set arbitrary variables or tags using a rewrite: rewrite r_my_tags_and_vars { set-tag('foo'); set('foo', value('bar')); }; In your particular example, you could also use the existing FILE_NAME macro. Cheers
Can you expand on how the FILE_NAME macro could be used? I don't understand how it could be helpful. The documentation says it the location where syslog-ng received the message. The messages are coming from a network source, my goal is to categorize them into separate files on the filesystem based on various filter matches. I must be missing something. Thanks, -Mark Mark Faine System Administrator SAIC/NICS 215 Wynn Dr. 5065 Huntsville, AL 35805 256-961-1295 (Desk) 256-617-4861 (Work Cell) -----Original Message----- From: syslog-ng <syslog-ng-bounces@lists.balabit.hu> On Behalf Of Fabien Wernli Sent: Monday, March 25, 2019 3:39 AM To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Subject: Re: [syslog-ng] Setting and using variables Hi Mark, On Fri, Mar 22, 2019 at 01:37:29PM +0000, Faine, Mark R. (MSFC-IS40)[NICS] wrote:
Is there a way to set variables in syslog-ng?
You can set arbitrary variables or tags using a rewrite: rewrite r_my_tags_and_vars { set-tag('foo'); set('foo', value('bar')); }; In your particular example, you could also use the existing FILE_NAME macro. Cheers ______________________________________________________________________________ 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...
participants (3)
-
Fabien Wernli
-
Faine, Mark R. (MSFC-IS40)[NICS]
-
Péter, Kókai