-
Notifications
You must be signed in to change notification settings - Fork 249
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
JSON parsing extension (DOC for rsyslog PR/#2773) #691
Conversation
The build failed with this error... Could you please enlighten me what was wrong in this PR? Thanks!! |
@@ -87,7 +87,7 @@ Note: parameter names are case-insensitive. | |||
|
|||
*(Available since: 8.5.1)* | |||
|
|||
Specifies if a variable insteed of property 'msg' should be used for | |||
Specifies if a variable insted of property 'msg' should be used for |
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.
instead
@nhosoi try rebasing on top of the latest master |
Adding parse_json extension "json_parse_ex" which supports compact.
03fb4fa
to
b7e64c2
Compare
Thank you, @richm. I thought I fixed it when I copied the section from mmnormalize, but I added another typo. :p Fixed both.
Regarding "rebasing on top of the latest master", I've done that just before creating this pr. So, it's up to date... |
/retest |
That's apparently a race in the github notification API. We see this occasionally. It looks like the commit is not actually available on all github front-end servers at the time the notification is sent out. If buildbot then starts up very quickly, we can hit that problem. We are investigating how to work-around it. Most probably, we will just add an initial "sleep step" to the buildbot configs. |
Closing this Doc PR along with the primary PR.
|
This is an update for rsyslog/rsyslog#2773 containing the following changes: