Skip to content
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

[ResponseOps] Elasticsearch Query rule: handle is_partial in ES|QL queries #209408

Open
pmuellr opened this issue Feb 3, 2025 · 1 comment
Open
Labels
Feature:Alerting/RuleTypes Issues related to specific Alerting Rules Types Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@pmuellr
Copy link
Member

pmuellr commented Feb 3, 2025

From https://elasticco.atlassian.net/browse/ES-8808, ES|QL results will start coming back with an is_partial flag set, if for some reason the query could not be completed but there are some results. The information about skipped clusters will come back in the _clusters metadata property.

My guess is, that because the info is coming back in the _clusters metadata, we're already handling it with the code we merged here: PR #189312

We should check to see if this is true (wonder how we can check?). We may want to also actually check the is_partial field explicitly here, as it sounds like it may be used in the future in other cases.

If this works with the existing code, the rule would process the returned (partial) results but generate a warning. I assume that behavior is still what we want ...

@pmuellr pmuellr added Feature:Alerting Feature:Alerting/RuleTypes Issues related to specific Alerting Rules Types Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Feb 3, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Alerting/RuleTypes Issues related to specific Alerting Rules Types Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

2 participants