Skip to content
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

Decoder RFC 5424 does not correctly parse structured data #61

Closed
gearnode opened this issue Nov 22, 2021 · 2 comments
Closed

Decoder RFC 5424 does not correctly parse structured data #61

gearnode opened this issue Nov 22, 2021 · 2 comments
Labels

Comments

@gearnode
Copy link

The decoder RFC 5424 does not correctly parse structured data. Currently, the parser parses only one structured data, which completely breaks the specification. As defined by the RFC 5424 ABF a Syslog message can contain no, one or more than one structured data.

Here is an example of a not properly parsed message:

<165>1 2003-10-11T22:14:15.003Z mymachine.example.com evntslog - ID47 [exampleSDID@32473 iut="3" eventSource= "Application" eventID="1011"][examplePriority@32473 class="high"] hello world

In this example, the message contains two structured data (but we can have a message with more than two) but the flowgger decoder only parses the first one and consider the rest a message, which is not correct too as the structured data and the message must be separated with a space.

@vche
Copy link
Contributor

vche commented Nov 22, 2021

Hi,
That is absolutely correct, thanks for raising this. I'll provide a fix for this as soon as possible.

@vche
Copy link
Contributor

vche commented Nov 24, 2021

Fixed in rev 0.2.12

@vche vche closed this as completed Nov 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants