[DataViews] Evaluate switching logs.alert.document.count alerting rule to make use of DataViewLazy #179128
Labels
impact:high
Addressing this issue will have a high 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
R&D
Research and development ticket (not meant to produce code, but to make a decision)
Team:DataDiscovery
Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.
Team:obs-ux-management
Observability Management User Experience Team
technical debt
Improvement of the software architecture and operational architecture
When DataViewLazy is implemented (#167750), the
logs.alert.document.count
rule 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 for the rule execution, this saves a lot of redundant requests to Elasticsearch.Here's the code to investigate:
kibana/x-pack/plugins/observability_solution/infra/server/lib/alerting/log_threshold/log_threshold_executor.ts
Lines 203 to 210 in ad272c2
Resolving the data view, which leads to a field_caps request is being used in rules execution and UI, and can be found here:
kibana/x-pack/plugins/observability_solution/logs_shared/common/log_views/resolved_log_view.ts
Lines 30 to 40 in 34e03d1
The text was updated successfully, but these errors were encountered: