mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 09:19:04 -04:00
Update aggregation reference docs for 7.13 (#101913)
* Update aggregation reference docs for 7.13 * Add more reference about filtered metrics
This commit is contained in:
parent
d7d67df5eb
commit
542fe02e1f
2 changed files with 24 additions and 8 deletions
|
@ -188,6 +188,12 @@ For information about {es} metrics aggregations, refer to {ref}/search-aggregati
|
|||
|
||||
| Type | Agg-based | Markdown | Lens | TSVB
|
||||
|
||||
| Metrics with filters
|
||||
|
|
||||
^| X
|
||||
|
|
||||
|
|
||||
|
||||
| Average
|
||||
^| X
|
||||
^| X
|
||||
|
@ -221,7 +227,7 @@ For information about {es} metrics aggregations, refer to {ref}/search-aggregati
|
|||
| Percentiles
|
||||
^| X
|
||||
^| X
|
||||
|
|
||||
^| X
|
||||
^| X
|
||||
|
||||
| Percentiles Rank
|
||||
|
@ -230,10 +236,10 @@ For information about {es} metrics aggregations, refer to {ref}/search-aggregati
|
|||
|
|
||||
^| X
|
||||
|
||||
| Top hit
|
||||
| Top hit (Last value)
|
||||
^| X
|
||||
^| X
|
||||
^| X
|
||||
|
|
||||
^| X
|
||||
|
||||
| Value count
|
||||
|
@ -266,7 +272,7 @@ For information about {es} pipeline aggregations, refer to {ref}/search-aggregat
|
|||
| Derivative
|
||||
^| X
|
||||
^| X
|
||||
|
|
||||
^| X
|
||||
^| X
|
||||
|
||||
| Max bucket
|
||||
|
@ -290,13 +296,13 @@ For information about {es} pipeline aggregations, refer to {ref}/search-aggregat
|
|||
| Moving average
|
||||
^| X
|
||||
^| X
|
||||
|
|
||||
^| X
|
||||
^| X
|
||||
|
||||
| Cumulative sum
|
||||
^| X
|
||||
^| X
|
||||
|
|
||||
^| X
|
||||
^| X
|
||||
|
||||
| Bucket script
|
||||
|
|
|
@ -147,14 +147,24 @@ For the answers to common *Lens* questions, review the following.
|
|||
|
||||
[float]
|
||||
[[kql-]]
|
||||
===== When should I use the Filter function instead of KQL filters?
|
||||
===== When should I use the top filter bar, filters function, or "Filter by"?
|
||||
|
||||
The easiest way to apply KQL filters is to use <<semi-structured-search>>, but you can also use the *Filters* function in the following scenarios:
|
||||
Using the top <<semi-structured-search>> bar is best when you want to focus on a known set of
|
||||
data for all the visualization results. These top level filters are combined with other filters
|
||||
using AND logic.
|
||||
|
||||
Use the *Filters* function in the following scenarios:
|
||||
|
||||
* When you want to apply more than one KQL filter to the visualization.
|
||||
|
||||
* When you want to apply the KQL filter to a single layer, which allows you to visualize filtered and unfiltered data.
|
||||
|
||||
Use the *Filter by* advanced option in the following scenarios:
|
||||
|
||||
* When you want to assign a custom color to each filter in a bar, line or area chart.
|
||||
|
||||
* When you want to build a complex table, such as showing both failure rate and overall.
|
||||
|
||||
[float]
|
||||
[[when-should-i-normalize-the-data-by-unit-or-use-a-custom-interval]]
|
||||
===== When should I normalize the data by unit or use a custom interval?
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue