-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Response Ops] Allow _source
field for ES DSL query rules
#142223
Conversation
Documentation preview: |
_source
field for ES DSL query rules
Pinging @elastic/response-ops (Team:ResponseOps) |
@elasticmachine merge upstream |
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! I was able to see _source returned in the context hits.
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @ymao1 |
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.
Tested locally and observed the expected result.
…142223) * Allowing _source in ES query DSL * Adding functional test * Adding to doc Co-authored-by: Kibana Machine <[email protected]>
…142223) * Allowing _source in ES query DSL * Adding functional test * Adding to doc Co-authored-by: Kibana Machine <[email protected]>
Resolves #124749
Summary
Allows users to specify
_source
field in their ES DSL query in order to filter the fields that are returned.To Verify
Create an ES query rule type using the different
_source
options available: https://www.elastic.co/guide/en/elasticsearch/reference/current/search-fields.html#source-filtering. Ensure that the source returned in thecontext.hits
variable is as expected. I used a server log action to log thecontext.hits
arrayChecklist