-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[http_endpoint input] Add support for including headers and preserving original events #26279
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
This pull request is now in conflicts. Could you fix it? 🙏
|
…lus/beats into httpendpoint_header_original
…g original events (#26279) * adding header support and event.original for the http_endpoint input * add changelog * updating docs * adding tests * applying comments from PR * adding more tests, and applying changes related to PR comments * linting * stashing changes * small changes * Linting * adding comments from PR (cherry picked from commit 794df17)
…g original events (#26279) (#26417) * adding header support and event.original for the http_endpoint input * add changelog * updating docs * adding tests * applying comments from PR * adding more tests, and applying changes related to PR comments * linting * stashing changes * small changes * Linting * adding comments from PR (cherry picked from commit 794df17) Co-authored-by: Marius Iversen <[email protected]>
What does this PR do?
This adds the possibility to give a list of headers that, if they exist in the incoming request, will be added as a separate object. Also adds the possibility to preserve the raw event as part of event.original.
Example output here:
Config example:
Why is it important?
Certain modules is hard to parse data without the extra details from the headers, github webhooks is one example of that, in which the data type is stored in the header
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.