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

[Alerting] Expensive queries by the alerting framework are causing unnecessary load and delays on Elasticsearch #121563

Closed
mikecote opened this issue Dec 17, 2021 · 2 comments · Fixed by #126111
Assignees
Labels
Feature:Alerting/RuleTypes Issues related to specific Alerting Rules Types Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

Based on #93770, we should convert https://github.com/elastic/kibana/blob/8.0/x-pack/plugins/triggers_actions_ui/public/common/lib/data_apis.ts#L66 to use _search_after instead of setting a large size value.

@mikecote mikecote added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Alerting/RuleTypes Issues related to specific Alerting Rules Types labels Dec 17, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@mikecote mikecote removed the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Jan 13, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 13, 2022
@mikecote mikecote added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed needs-team Issues missing a team label labels Jan 13, 2022
@elasticmachine
Copy link
Contributor

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

@mikecote mikecote changed the title [Alerting] Expensive queries are causing unnecessary load and delays on Elasticsearch [Alerting] Expensive queries by the alerting framework are causing unnecessary load and delays on Elasticsearch Jan 24, 2022
@kobelb kobelb removed the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Jan 31, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 31, 2022
@kobelb kobelb added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
@ersin-erdal ersin-erdal self-assigned this Feb 16, 2022
@ersin-erdal ersin-erdal moved this from In Progress to In Review in AppEx: ResponseOps - Execution & Connectors Feb 22, 2022
Repository owner moved this from In Review to Done in AppEx: ResponseOps - Execution & Connectors Mar 4, 2022
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 Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

4 participants