Add configuration option for RFC 5424 Structured Data #48
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
…tution values. Default remains "-", but it is no longer hardcoded and unchangeable. Note that this will not create structured data from a list of fields, but it will allow you to format your own SD block.
…ssage length header as specified in RFC 5425 for TLS (also used by rsyslog and syslog-ng for TCP syslog drivers.
|
Unnecessary now that #65 has been merged. |
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.
In this code the structured_data is string, assumed to meet the RFC, or defaults to a "-". You will have to add the structured data ID and brackets around each structured data element.
Usage example:
structured_data => '[[email protected] position="%{file_pos}" size="%{file_size}" name="%{file_name}"]'Where file_pos, file_size, and file_name are fields in the event.