Details
-
Type:
Task
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 28.0.0
-
Component/s: None
-
Security Level: Default (Default Security Scheme)
-
Labels:None
-
Epic Link:
-
Sprint:Horizon 2021 - Jan 20 - Feb 3, Horizon 2021 - Feb 3 - Feb 17, Horizon 2021 - Feb 17 - Mar 3, Horizon 2021 - Mar 3 - Mar 17, Horizon 2021 - Mar 17 - Mar 31, Horizon 2021 - Mar 31 - Apr 14, Horizon 2021 - Apr 14 - Apr 28, Horizon 2021 - May 12 - May 26
-
HB Backlog Status:Backlog NG
Description
When topK flow summaries/series are queried for applications, conversation, or hosts and no DSCP or ECN filter exists then precalculated aggregations for
- exporter/interface
- exporter/interface/dscp
- exporter/interface/ecn
could be used as the parent "aggregation" for calculating the contribution of "Other" application, conversation, or hosts (cf.NMS-12946).
These additional topK aggregations could be calculated for applications, conversations, and host:
- exporter/interface/application, exporter/interface/conversation, exporter/interface/host
- exporter/interface/dscp/application, exporter/interface/dscp/conversation, exporter/interface/dscp/host
- exporter/interface/ecn/application, exporter/interface/ecn/conversation, exporter/interface/ecn/host
However, this means a lot more storage for reduced query time work.
Another optimization may be to store different aggregations in different indexes ("Split your data into multiple indices if your query has a filter field and its value is enumerable."; cf. https://tech.ebayinc.com/engineering/elasticsearch-performance-tuning-practice-at-ebay/)