Add RFC5424 format support for syslog input#20246
Add RFC5424 format support for syslog input#20246wph95 wants to merge 11 commits intoelastic:masterfrom
Conversation
- add VERSION schema
|
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
1 similar comment
|
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
|
💚 CLA has been signed |
❕ Build Aborted
Expand to view the summary
Build stats
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
- clean code - change parser.go to parser/parser_rfc5424
- Add "ProcID" format - Add "MsgID" format - Add "HostName" format - improve test
|
Related: #15467 |
|
Pinging @elastic/integrations-services (Team:Services) |
- add auto detect format
|
Major code logic and core test completed |
- add more test
# Conflicts: # filebeat/input/syslog/rfc3164_parser.go
|
Hi! We're labeling this issue as |
|
Hi! |
|
@wph95 Hi! Could you re-open PR, please? |
What does this PR do?
Resolves #6872
Add RFC5424 format support for syslog input
Why is it important?
Syslog input only support rfc3164, btw rfc3164 is obsoleted by rfc5424
More and more software is using rfc5424 instead of rfc3164.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Related issues
closes # #6872
Use cases
Screenshots
Logs