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

RFC5424 support? #31

Open
l29ah opened this issue Feb 4, 2024 · 7 comments
Open

RFC5424 support? #31

l29ah opened this issue Feb 4, 2024 · 7 comments

Comments

@l29ah
Copy link

l29ah commented Feb 4, 2024

metalog seems to ignore syslog messages sent to /dev/log that satisfy the RFC.

Is there a doc on what kind of syntax does metalog actually expect?

@m-kress
Copy link
Collaborator

m-kress commented Mar 9, 2024

Do you have an example, what syslog message sent to /dev/log gets ignored?

The only doc regarding the syntax seems to be the code. What exactly is the issue?

@l29ah
Copy link
Author

l29ah commented Mar 9, 2024

My real issue is haskell-hvr/hslogger#17 (that is also not-RFC5424 tho).
I don't have an example at hand rn.

@m-kress
Copy link
Collaborator

m-kress commented Mar 9, 2024

It would be very helpful having an example that works with syslog-ng and not with metalog.
In metalog.c that line might get eliminated in parseLogLine()

@l29ah
Copy link
Author

l29ah commented Mar 9, 2024

Built an example from that issue report, it yields this in strace: [pid 5717] sendto(16, "<11>: [/ERROR] This won't show up with metalog.\0", 48, 0, NULL, 0) = 48.

@m-kress
Copy link
Collaborator

m-kress commented Mar 9, 2024

It seems as metalog expects a ":" after the [xyz], e.g.
<11>: [/ERROR]: This might show up with metalog

Obviously metalog has been loosely written for RFC3164 (BSD syslog).

@l29ah
Copy link
Author

l29ah commented Mar 9, 2024

Adding a ":" doesn't change the behavior it seems.

@m-kress m-kress mentioned this issue Jul 12, 2024
@m-kress
Copy link
Collaborator

m-kress commented Jul 12, 2024

You could test again with ": " (space after colon).
Metalog works like described in RFC3164, not like the predecessor RFC5424. Please also look at the other issue #32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants