-
Notifications
You must be signed in to change notification settings - Fork 473
[udp,tcp]: introduce preserve original event option #10474
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
[udp,tcp]: introduce preserve original event option #10474
Conversation
d97e85b
to
b75e3b0
Compare
Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices) |
b75e3b0
to
107f248
Compare
107f248
to
c705070
Compare
@andrewkroh any idea how to deal with coverage issue? I have added test cases for syslog+preserve_original_event and preserve_original_event alone so I am not sure what else I can do to increase it 😄 |
This looks like a problem with that's occurring on several PRs. It seems like the changelog.yml and manifest.yml are being scored with 0% coverage bringing down overall value. There was an email about updating PRs with main to address Sonarqube failures. Give that a try. |
…asilis/tcp_udp_preserve_original_event
|
💚 Build Succeeded
History
|
You can merge this according to #10225 (comment) |
Package tcp - 1.19.1 containing this change is available at https://epr.elastic.co/search?package=tcp |
Package udp - 1.19.1 containing this change is available at https://epr.elastic.co/search?package=udp |
Proposed commit message
This PR introduces the
preserve_event_original
option forudp
andtcp
integrations. This is especially useful when a user has enabled the "Syslog Parser" toggle as there's no way to retain the original message because the syslog processor will overwrite messageChecklist
changelog.yml
file.Author's Checklist
N/A
How to test this PR locally
Related issues
Screenshots