[DataViews] Evaluate switching ML alert rules to make use of DataViewLazy #173996
Closed
Labels
Feature:Data Views
Data Views code and UI - index patterns before 8.0
impact:medium
Addressing this issue will have a medium level of impact on the quality/strength of our product.
loe:needs-research
This issue requires some research before it can be worked on or estimated
:ml
Team:DataDiscovery
Discover App Team (Document Explorer, Saved Search, Surrounding documents, Graph)
technical debt
Improvement of the software architecture and operational architecture
v8.16.0
When DataViewLazy is implemented (#167750), ML based alerting rules should be evaluated to consume this new class. The benefit of it is that it's no longer triggering a request for fields (field_caps request to ES) when being initialized. When fields are not needed, this saves a lot of redundant requests to Elasticsearch. At the first sight it seems the DataView service is needed to get the
fieldFormatMap
. For this the requests for fields should not be necessary:kibana/x-pack/plugins/ml/server/lib/alerts/alerting_service.ts
Lines 217 to 234 in 50dabea
The text was updated successfully, but these errors were encountered: