[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 |
* feat(tcp): introduce preserve original event option * feat(udp): introduce preserve original event option


Proposed commit message
This PR introduces the
preserve_event_originaloption forudpandtcpintegrations. 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.ymlfile.Author's Checklist
N/A
How to test this PR locally
Related issues
Screenshots