From 56815bd031655544bc6e116e8858e2f6c21d00c9 Mon Sep 17 00:00:00 2001 From: Florent LB Date: Fri, 19 Jun 2026 21:09:18 +0200 Subject: [PATCH 1/9] docs: document Use global filters option for ES|QL layers (#6351) Co-authored-by: Cursor --- explore-analyze/visualize/esorql.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/explore-analyze/visualize/esorql.md b/explore-analyze/visualize/esorql.md index eb508ee6d0..f5ebbc2ad6 100644 --- a/explore-analyze/visualize/esorql.md +++ b/explore-analyze/visualize/esorql.md @@ -130,6 +130,16 @@ serverless: ga Drilldowns can only be triggered from values backed by a field that exists in the underlying index. Values produced by {{esql}} commands like `EVAL` or `STATS` are not backed by an index field, so the drilldown option is not available when you click on those columns or series. For more information, refer to [Add pills by interacting with visualizations](../dashboards/using.md#_add_pills_by_interacting_with_visualizations). +## Ignore global filters [esql-viz-ignore-global-filters] +```{applies_to} +stack: ga 9.5 +serverless: ga +``` + +By default, an {{esql}} visualization responds to the global filters and the KQL or Lucene query applied at the dashboard level. You can make a layer run its query independently of that context, so it always returns the same data regardless of the dashboard's filters and query. + +To do this, select the {icon}`gear` **Settings** icon on the layer header, then turn off **Use global filters**. This option mirrors the equivalent setting available on form-based layers. + ## Create an alert from your {{esql}} visualization ```{applies_to} stack: ga 9.1 From 9a7e87ede578c6744ba7eb360aec2396427e13f3 Mon Sep 17 00:00:00 2001 From: Florent LB Date: Fri, 19 Jun 2026 21:22:32 +0200 Subject: [PATCH 2/9] docs: clarify Use global filters behavior for ES|QL layers (#6351) Co-authored-by: Cursor --- explore-analyze/visualize/esorql.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/explore-analyze/visualize/esorql.md b/explore-analyze/visualize/esorql.md index f5ebbc2ad6..0d87619c7d 100644 --- a/explore-analyze/visualize/esorql.md +++ b/explore-analyze/visualize/esorql.md @@ -136,9 +136,9 @@ stack: ga 9.5 serverless: ga ``` -By default, an {{esql}} visualization responds to the global filters and the KQL or Lucene query applied at the dashboard level. You can make a layer run its query independently of that context, so it always returns the same data regardless of the dashboard's filters and query. +By default, an {{esql}} visualization responds to the global filters and the KQL or Lucene query applied at the dashboard level. You can configure a layer to run its query independently of that context. -To do this, select the {icon}`gear` **Settings** icon on the layer header, then turn off **Use global filters**. This option mirrors the equivalent setting available on form-based layers. +To do this, select the {icon}`gear` **Settings** icon on the layer header, then turn off **Use global filters**. The layer then ignores the dashboard filters and the KQL or Lucene query, and always returns the same data. The dashboard time range still applies. ## Create an alert from your {{esql}} visualization ```{applies_to} From 8eba4b658b60e3bd183f0c8ea08f0ea20e6ba098 Mon Sep 17 00:00:00 2001 From: Florent LB Date: Fri, 19 Jun 2026 21:24:51 +0200 Subject: [PATCH 3/9] docs: clarify time range still applies for ES|QL global filters (#6351) Co-authored-by: Cursor --- explore-analyze/visualize/esorql.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/explore-analyze/visualize/esorql.md b/explore-analyze/visualize/esorql.md index 0d87619c7d..2d68febe4b 100644 --- a/explore-analyze/visualize/esorql.md +++ b/explore-analyze/visualize/esorql.md @@ -138,7 +138,7 @@ serverless: ga By default, an {{esql}} visualization responds to the global filters and the KQL or Lucene query applied at the dashboard level. You can configure a layer to run its query independently of that context. -To do this, select the {icon}`gear` **Settings** icon on the layer header, then turn off **Use global filters**. The layer then ignores the dashboard filters and the KQL or Lucene query, and always returns the same data. The dashboard time range still applies. +To do this, select the {icon}`gear` **Settings** icon on the layer header, then turn off **Use global filters**. The layer then ignores the dashboard filters and the KQL or Lucene query. It still respects the dashboard time range, but is otherwise unaffected by the dashboard context. ## Create an alert from your {{esql}} visualization ```{applies_to} From 5974728f9a34fedf3ecfcbeecacf85d258196663 Mon Sep 17 00:00:00 2001 From: Florent LB Date: Fri, 19 Jun 2026 21:29:45 +0200 Subject: [PATCH 4/9] docs: scope what global filters means for ES|QL layers (#6351) Co-authored-by: Cursor --- explore-analyze/visualize/esorql.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/explore-analyze/visualize/esorql.md b/explore-analyze/visualize/esorql.md index 2d68febe4b..0005557d53 100644 --- a/explore-analyze/visualize/esorql.md +++ b/explore-analyze/visualize/esorql.md @@ -136,9 +136,9 @@ stack: ga 9.5 serverless: ga ``` -By default, an {{esql}} visualization responds to the global filters and the KQL or Lucene query applied at the dashboard level. You can configure a layer to run its query independently of that context. +By default, an {{esql}} visualization applies the global filters and the KQL or Lucene query set at the dashboard level. To make a layer run its query independently of them, select the {icon}`gear` **Settings** icon on the layer header, then turn off **Use global filters**. -To do this, select the {icon}`gear` **Settings** icon on the layer header, then turn off **Use global filters**. The layer then ignores the dashboard filters and the KQL or Lucene query. It still respects the dashboard time range, but is otherwise unaffected by the dashboard context. +Here, *global filters* means the dashboard's filter pills and the query from the search bar. The dashboard time range is a separate control that always applies, whether or not **Use global filters** is turned on. ## Create an alert from your {{esql}} visualization ```{applies_to} From ff2486e97cf8b5aa90ec77818689c9bedebdcdfd Mon Sep 17 00:00:00 2001 From: Florent LB Date: Fri, 19 Jun 2026 21:31:28 +0200 Subject: [PATCH 5/9] docs: use dashboard filters in prose for ES|QL setting (#6351) Co-authored-by: Cursor --- explore-analyze/visualize/esorql.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/explore-analyze/visualize/esorql.md b/explore-analyze/visualize/esorql.md index 0005557d53..65ecf9c454 100644 --- a/explore-analyze/visualize/esorql.md +++ b/explore-analyze/visualize/esorql.md @@ -130,15 +130,15 @@ serverless: ga Drilldowns can only be triggered from values backed by a field that exists in the underlying index. Values produced by {{esql}} commands like `EVAL` or `STATS` are not backed by an index field, so the drilldown option is not available when you click on those columns or series. For more information, refer to [Add pills by interacting with visualizations](../dashboards/using.md#_add_pills_by_interacting_with_visualizations). -## Ignore global filters [esql-viz-ignore-global-filters] +## Ignore dashboard filters [esql-viz-ignore-dashboard-filters] ```{applies_to} stack: ga 9.5 serverless: ga ``` -By default, an {{esql}} visualization applies the global filters and the KQL or Lucene query set at the dashboard level. To make a layer run its query independently of them, select the {icon}`gear` **Settings** icon on the layer header, then turn off **Use global filters**. +By default, an {{esql}} visualization applies the filters and the KQL or Lucene query set at the dashboard level. To make a layer run its query independently of them, select the {icon}`gear` **Settings** icon on the layer header, then turn off **Use global filters**. -Here, *global filters* means the dashboard's filter pills and the query from the search bar. The dashboard time range is a separate control that always applies, whether or not **Use global filters** is turned on. +This option covers the dashboard's filter pills and the query from the search bar. The dashboard time range is a separate control that always applies, whether or not the option is turned on. ## Create an alert from your {{esql}} visualization ```{applies_to} From 41f6d846d95622c21270737dc04376bc8aedf1cf Mon Sep 17 00:00:00 2001 From: Florent LB Date: Fri, 19 Jun 2026 21:38:27 +0200 Subject: [PATCH 6/9] docs: reflect Layer settings rename to Settings and fix icon (#6351) Co-authored-by: Cursor --- explore-analyze/visualize/lens.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/explore-analyze/visualize/lens.md b/explore-analyze/visualize/lens.md index 8c6f630565..e029956664 100644 --- a/explore-analyze/visualize/lens.md +++ b/explore-analyze/visualize/lens.md @@ -274,7 +274,7 @@ To create partition charts, such as pie charts, configure one or more **Slice by For detailed instructions on creating pie charts, including best practices and configuration options, refer to [Build pie charts with {{kib}}](/explore-analyze/visualize/charts/pie-charts.md). -1. In the layer pane, click ![Actions menu for the partition visualization layer](/explore-analyze/images/kibana-lens_layerActions_8.5.0.png ""), then select **Layer settings**. +1. In the layer pane, click ![Actions menu for the partition visualization layer](/explore-analyze/images/kibana-lens_layerActions_8.5.0.png ""), then select **Settings**/**Layer settings**. 2. Select **Multiple metrics**. 3. Click **X**. @@ -284,7 +284,7 @@ For detailed instructions on creating pie charts, including best practices and c stack: preview ``` -Data sampling allows you to improve the visualization loading time. When you can create your visualization, click the **Layer settings** icon {icon}`app_management` and use the slider to adjust the **Sampling** percentage. For example, on large datasets, you can decrease the loading time by using a lower sampling percentage. This increases performance but lowers the accuracy. +Data sampling allows you to improve the visualization loading time. When you can create your visualization, click the **Settings**/**Layer settings** icon {icon}`gear` and use the slider to adjust the **Sampling** percentage. For example, on large datasets, you can decrease the loading time by using a lower sampling percentage. This increases performance but lowers the accuracy. ### Add annotations [add-annotations] @@ -299,7 +299,7 @@ Click the **Add layer** icon {icon}`plus_square` , select **Annotations** and se 1. Select the {{data-source}} for the annotation. 2. From the fields list, drag a field to the **Horizontal axis** field. -To use global filters in the annotation, click the **Layer settings** icon {icon}`app_management` on the annotations layer, and select **Use global filters**. +To use global filters in the annotation, click the **Settings**/**Layer settings** icon {icon}`gear` on the annotations layer, and select **Use global filters**. From the annotation panel, you can choose the type of placement and adjust the its appearance. From 51ba72f06ded7ab9ab7e61804f705fc627b2145d Mon Sep 17 00:00:00 2001 From: Florent LB Date: Fri, 19 Jun 2026 21:53:40 +0200 Subject: [PATCH 7/9] docs: apply Settings rename and gear icon to pie and waffle layer settings (#6351) Co-authored-by: Cursor --- explore-analyze/visualize/charts/pie-charts.md | 6 +++--- explore-analyze/visualize/charts/waffle-charts.md | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/explore-analyze/visualize/charts/pie-charts.md b/explore-analyze/visualize/charts/pie-charts.md index 99261f7bf8..d79f7526e3 100644 --- a/explore-analyze/visualize/charts/pie-charts.md +++ b/explore-analyze/visualize/charts/pie-charts.md @@ -221,10 +221,10 @@ This is useful when: This example uses the **Kibana Sample Data Logs** data set and groups requests by file extension to approximate resource usage: `.zip` files map to processing time, `.gz` files map to bandwidth, and `.rpm` files map to memory usage. 1. Create a **Pie** chart and remove any existing **Slice by** dimension. -2. Open **Layer settings**: - * {applies_to}`serverless: ga` {applies_to}`stack: ga 9.3` Select {icon}`app_management` **Layer settings**. +2. Open **Settings**/**Layer settings**: + * {applies_to}`serverless: ga` {applies_to}`stack: ga 9.3` Select {icon}`gear` **Settings**/**Layer settings**. * {applies_to}`stack: ga 9.0-9.2` Select {icon}`boxes_vertical`, then select **Layer settings**. -3. Select **Multiple metrics**, then close the **Layer settings** menu. +3. Select **Multiple metrics**, then close the **Settings**/**Layer settings** menu. 4. Add metrics for each resource type: | Slice | Metric configuration | Filter | diff --git a/explore-analyze/visualize/charts/waffle-charts.md b/explore-analyze/visualize/charts/waffle-charts.md index 71fdf0378f..6e47d30893 100644 --- a/explore-analyze/visualize/charts/waffle-charts.md +++ b/explore-analyze/visualize/charts/waffle-charts.md @@ -85,8 +85,8 @@ You can use **Multiple metrics** to show progress toward a goal, with filled squ This example uses the **Kibana Sample Data eCommerce** data set. If you haven't installed it yet, refer to [Sample data](/manage-data/ingest/sample-data.md) for instructions. 1. Create a **Waffle** chart using the **Kibana Sample Data eCommerce** {{data-source}}. -2. Open **Layer settings**: - * {applies_to}`serverless: ga` {applies_to}`stack: ga 9.3` Select {icon}`app_management` **Layer settings**. +2. Open **Settings**/**Layer settings**: + * {applies_to}`serverless: ga` {applies_to}`stack: ga 9.3` Select {icon}`gear` **Settings**/**Layer settings**. * {applies_to}`stack: ga 9.0-9.2` Select {icon}`boxes_horizontal`, then select **Layer settings**. 3. Select **Multiple metrics**, then close the layer settings. 4. Add two metrics: From 55efe8d339e9926d6e1dbbfd48d956301d27e428 Mon Sep 17 00:00:00 2001 From: Florent LB Date: Fri, 19 Jun 2026 21:58:37 +0200 Subject: [PATCH 8/9] docs: keep layer settings step lead-ins generic in pie and waffle (#6351) Co-authored-by: Cursor --- explore-analyze/visualize/charts/pie-charts.md | 4 ++-- explore-analyze/visualize/charts/waffle-charts.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/explore-analyze/visualize/charts/pie-charts.md b/explore-analyze/visualize/charts/pie-charts.md index d79f7526e3..10f05fba32 100644 --- a/explore-analyze/visualize/charts/pie-charts.md +++ b/explore-analyze/visualize/charts/pie-charts.md @@ -221,10 +221,10 @@ This is useful when: This example uses the **Kibana Sample Data Logs** data set and groups requests by file extension to approximate resource usage: `.zip` files map to processing time, `.gz` files map to bandwidth, and `.rpm` files map to memory usage. 1. Create a **Pie** chart and remove any existing **Slice by** dimension. -2. Open **Settings**/**Layer settings**: +2. Open the layer settings: * {applies_to}`serverless: ga` {applies_to}`stack: ga 9.3` Select {icon}`gear` **Settings**/**Layer settings**. * {applies_to}`stack: ga 9.0-9.2` Select {icon}`boxes_vertical`, then select **Layer settings**. -3. Select **Multiple metrics**, then close the **Settings**/**Layer settings** menu. +3. Select **Multiple metrics**, then close the layer settings menu. 4. Add metrics for each resource type: | Slice | Metric configuration | Filter | diff --git a/explore-analyze/visualize/charts/waffle-charts.md b/explore-analyze/visualize/charts/waffle-charts.md index 6e47d30893..a63df74ae0 100644 --- a/explore-analyze/visualize/charts/waffle-charts.md +++ b/explore-analyze/visualize/charts/waffle-charts.md @@ -85,7 +85,7 @@ You can use **Multiple metrics** to show progress toward a goal, with filled squ This example uses the **Kibana Sample Data eCommerce** data set. If you haven't installed it yet, refer to [Sample data](/manage-data/ingest/sample-data.md) for instructions. 1. Create a **Waffle** chart using the **Kibana Sample Data eCommerce** {{data-source}}. -2. Open **Settings**/**Layer settings**: +2. Open the layer settings: * {applies_to}`serverless: ga` {applies_to}`stack: ga 9.3` Select {icon}`gear` **Settings**/**Layer settings**. * {applies_to}`stack: ga 9.0-9.2` Select {icon}`boxes_horizontal`, then select **Layer settings**. 3. Select **Multiple metrics**, then close the layer settings. From a50b065bbbe63e989af514db9cc3c75865482e7a Mon Sep 17 00:00:00 2001 From: Florent LB Date: Tue, 23 Jun 2026 11:07:18 +0200 Subject: [PATCH 9/9] Apply suggestions from code review Co-authored-by: Liam Thompson --- explore-analyze/visualize/esorql.md | 4 +++- explore-analyze/visualize/lens.md | 2 +- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/explore-analyze/visualize/esorql.md b/explore-analyze/visualize/esorql.md index 65ecf9c454..af98e83a51 100644 --- a/explore-analyze/visualize/esorql.md +++ b/explore-analyze/visualize/esorql.md @@ -136,7 +136,9 @@ stack: ga 9.5 serverless: ga ``` -By default, an {{esql}} visualization applies the filters and the KQL or Lucene query set at the dashboard level. To make a layer run its query independently of them, select the {icon}`gear` **Settings** icon on the layer header, then turn off **Use global filters**. +By default, an {{esql}} visualization applies the filters and the KQL or Lucene query set at the dashboard level. To force a layer to run its query without these filters: +1. Select the {icon}`gear` **Settings** icon on the layer header. +2. Turn off **Use global filters**. This option covers the dashboard's filter pills and the query from the search bar. The dashboard time range is a separate control that always applies, whether or not the option is turned on. diff --git a/explore-analyze/visualize/lens.md b/explore-analyze/visualize/lens.md index e029956664..e51c72423d 100644 --- a/explore-analyze/visualize/lens.md +++ b/explore-analyze/visualize/lens.md @@ -284,7 +284,7 @@ For detailed instructions on creating pie charts, including best practices and c stack: preview ``` -Data sampling allows you to improve the visualization loading time. When you can create your visualization, click the **Settings**/**Layer settings** icon {icon}`gear` and use the slider to adjust the **Sampling** percentage. For example, on large datasets, you can decrease the loading time by using a lower sampling percentage. This increases performance but lowers the accuracy. +Data sampling allows you to improve the visualization loading time. When you create your visualization, click the **Settings**/**Layer settings** icon {icon}`gear` and use the slider to adjust the **Sampling** percentage. For example, on large datasets, you can decrease loading time by using a lower sampling percentage. This increases performance but reduces accuracy. ### Add annotations [add-annotations]