Add RFC 5424 extractors, update README #11
Merged
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.
When I tried using these extractors in my environment, the timestamps were incorrect (OPNsense was sending timestamps in its local time zone). When I configured OPNsense to send RFC 5424-compliant logs instead, the timestamp issue was fixed, but the extractors could no longer parse the logs, particularly because
filterlog
was now being parsed out into theapplication_name
field (and therefore was no longer present in themessage
field). This necessitates instructing Graylog to save the full message, as detailed in the updated README.I updated the regexes to match the different RFC-compliant format, which looks something like this (example is an IPv6 ICMP message). Note the inclusion of the
meta
structured data ID - this meant changing the regex to match anything in brackets, not just digits:Finally, it appears that OPNsense has switched from sending
ipv6-icmp
to justicmp
, so I fixed that up as well.Let me know if there's anything I should address, and thanks for developing these extractors!