Make log messages RFC5424 compliant #27
Open
Conversation
This file contains hidden or 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
add class to be compliant
Author
|
Some more stuff to read: https://sematext.com/what-is-syslog-daemons-message-formats-and-protocols/ |
simon-mueller
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Currently the log messages are containing timestamps that are not compliant with the standard for syslog messages. They're not even BSD (old standard) compliant.
In my remote syslog host, the logs were looking like this:
Link to RFC norm: https://datatracker.ietf.org/doc/html/rfc5424#autoid-13
This PR adds a new class that formats the timestamp correctly. In my remote syslog host they now look like this:
If the timestamp is contained inside the message column, I cannot aggregate them and they won't be counted properly.
Thanks in advance
Simon