New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tags-parser: new module to parse $TAGS values #1658
Conversation
Build SUCCESS, the tests were executed on test branch: master and test suite: functions |
@@ -0,0 +1,83 @@ | |||
/* | |||
* Copyright (c) 2002-2015 Balabit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The year in copyright can be updated to 2017. The other copyright sections look ok.
Looks ok to me. Once travis is green, I think we can merge this. |
I have now added unit tests, so this should be good enough for merging. |
Build SUCCESS, the tests were executed on test branch: master and test suite: functions |
@@ -0,0 +1,12 @@ | |||
modules_tagsparser_tests_TESTS = modules/tagsparser/tests/test_tagsparser |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add if ENABLE_CRITERION here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
Build SUCCESS, the tests were executed on test branch: master and test suite: functions |
Build SUCCESS, the tests were executed on test branch: master and test suite: functions |
1 similar comment
Build SUCCESS, the tests were executed on test branch: master and test suite: functions |
Build SUCCESS, the tests were executed on test branch: master and test suite: functions |
Signed-off-by: Balazs Scheidler <balazs.scheidler@balabit.com>
The new tags-parser() takes a value encoded by $TAGS and parses it back into actual tags on the message. Example: tags-parser(template("$PROGRAM")); Signed-off-by: Balazs Scheidler <balazs.scheidler@balabit.com>
Signed-off-by: Balazs Scheidler <balazs.scheidler@balabit.com>
Build SUCCESS, the tests were executed on test branch: master and test suite: functions |
We've discussed this IRL, is a standalone plugin with unit tests, so it is ready to go in. |
@fekete-robert This is a really nice feature that we forgot to add to the documentation. It is possible to forward
|
Thanks, I'll hopefully document it for 3.23
…On Thu, Aug 15, 2019 at 1:14 PM László Várady ***@***.***> wrote:
@fekete-robert <https://github.com/fekete-robert> This is a really nice
feature that we forgot to add to the documentation.
It is possible to forward $TAGS in syslog messages, the documentation
mentions this as a note:
https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edition/3.22/administration-guide/58#TOPIC-1209290
tags-parser() is the inverse of this functionality, it parses $TAGS back
to real tags.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1658>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA6AU3KQEKC5PSR53W7GHEDQEU3DDANCNFSM4DZQXISA>
.
|
@fekete-robert Thanks very much! |
The new tags-parser() takes a value encoded by $TAGS and parses it
back into actual tags on the message.
Example: