-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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] Lazy load dataViews and wrappedSearchSourceClient services when running alerting rules #189929
[ResponseOps] Lazy load dataViews and wrappedSearchSourceClient services when running alerting rules #189929
Conversation
/ci |
/ci |
/ci |
…m:doakalexi/kibana into alerting/lazy-load-dataviews-searchsource
/ci |
/ci |
…m:doakalexi/kibana into alerting/lazy-load-dataviews-searchsource
/ci |
Pinging @elastic/response-ops (Team:ResponseOps) |
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.
Obs ux management changes LGTM.
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
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.
DE changes LGTM
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.
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
Resolves #184322
Summary
This PR updates
getExecutorServices
to allow alerting rules to only load the dataViews and wrappedSearchSourceClient services when needed. I updated the rule types dependent on dataViews and/or wrappedSearchSourceClient.Checklist
To verify
dataViews
andsearchSourceClient
services are not created.Custom threshold
SLO burn rate
ES query
Indicator match