RFC5424Log structured data #53
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mmitucha
force-pushed
the
rfc5424structured
branch
from
b947d59
to
1ccee94
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added structured data part for rfc5424 log type according to https://datatracker.ietf.org/doc/html/rfc5424
Sample rfc5424 log:
the structured data
[exampleSDID@353664 iut="8" eventSource="Application" eventID="306249"][examplePriority@97903 class="high" method="POST" uri="/granular/sexy/integrate" status_code="504" time_millis="186" remote_host="128.200.83.221" remote_ip_addr="156.235.138.200"]consist of two parts inside square brackets(
[...][...]), which is valid and I think it is good for testing rfc5424 parser.