-
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
[Filebeat][httpjson] Adding possibility to use first_event in cursor context #23437
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
As discussed with @marc-gr , the new functionality still requires tests, as there is also no tests for |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
2fd5cf1
to
111e550
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…ts into filebeat_httpjson_first_event
…context (elastic#23437) * adding possibility to use first_event context in httpjson * fixing typo * Add transform context state test * updating changelog Co-authored-by: Marc Guasch <marc.guasch@elastic.co> (cherry picked from commit d4e85e0)
…context (#23437) (#23491) * adding possibility to use first_event context in httpjson * fixing typo * Add transform context state test * updating changelog Co-authored-by: Marc Guasch <marc.guasch@elastic.co> (cherry picked from commit d4e85e0) Co-authored-by: Marius Iversen <marius.iversen@elastic.co>
What does this PR do?
This PR extends the context to also support first_event, similar to last_event and last_response, this is to be able to support API's that returns the newest event first instead of last.
Why is it important?
Multiple modules are blocked while missing this functionality.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Closes #23358