Skip to content

Commit a433e16

Browse files
authored
Merge branch 'main' into 2025/11/26/s3-linearizable-register-9_3_0
2 parents 7e2d99c + 6a67222 commit a433e16

File tree

20 files changed

+202
-67
lines changed

20 files changed

+202
-67
lines changed

.gitignore

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,10 @@
99
# Add LLM/AI related files
1010
AGENTS.md
1111
.github/copilot-instructions.md
12-
.github/instructions/**.instructions.md
12+
.github/instructions
1313
CLAUDE.md
1414
GEMINI.md
1515
.cursor
1616

1717
# VS code settings
18-
.vscode
18+
.vscode

deploy-manage/api-keys/elastic-cloud-api-keys.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,9 +34,11 @@ These keys provides access to the API that enables you to manage your deployment
3434

3535
::::{note}
3636
When an API key is nearing expiration, Elastic sends an email to the creator of the API key and each of the operational contacts. When you use an API key to authenticate, the API response header `X-Elastic-Api-Key-Expiration` indicates the key’s expiration date. You can log this value to detect API keys that are nearing expiration.
37+
38+
Once an API key expires, it will automatically be removed from the API Keys tab.
3739
::::
3840

39-
5. Click **Create API key**, copy the generated API key, and store it in a safe place. You can also download the key as a CSV file.
41+
6. Click **Create API key**, copy the generated API key, and store it in a safe place. You can also download the key as a CSV file.
4042

4143
The API key needs to be supplied in the `Authorization` header of a request, in the following format:
4244

deploy-manage/deploy/cloud-on-k8s/pod-disruption-budget.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,12 +19,13 @@ In {{eck}} 3.1 and earlier, all clusters follow the [default PodDisruptionBudget
1919
:::
2020

2121
## Advanced rules (Enterprise license required)
22+
2223
```{applies_to}
2324
deployment:
2425
eck: ga 3.2
2526
```
2627

27-
In Elasticsearch clusters managed by ECK and licensed with an Enterprise license, a separate PDB is created for each type of `nodeSet` defined in the manifest. This setup allows Kubernetes upgrade or maintenance operations to be executed more quickly. Each PDB permits one Elasticsearch Pod per `nodeSet` to be disrupted at a time, provided the Elasticsearch cluster maintains the health status described in the following table:
28+
In {{es}} clusters managed by ECK and licensed with an Enterprise license, PDBs are created based on {{es}} node roles, allowing Kubernetes upgrade or maintenance operations to be executed more quickly. Multiple `nodeSets` with the same roles, such as `master` or `ml`, are combined into a single PDB. Each PDB permits one {{es}} Pod to be disrupted at a time, provided the {{es}} cluster maintains the health status described in the following table.
2829

2930
| Role | Cluster health required | Notes |
3031
|------|------------------------|--------|
@@ -40,6 +41,7 @@ In Elasticsearch clusters managed by ECK and licensed with an Enterprise license
4041
Single-node clusters are not considered highly available and can always be disrupted regardless of license type.
4142

4243
## Default rules (Basic license) [default-pdb-rules]
44+
4345
:::{note}
4446
In {{eck}} 3.1 and earlier, all clusters follow this behavior regardless of license type.
4547
:::

explore-analyze/discover.md

Lines changed: 39 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,17 +6,52 @@ applies_to:
66
serverless: ga
77
products:
88
- id: kibana
9+
description: Use Discover to search and filter documents, analyze field structures, visualize patterns, and save findings to reuse later or share with dashboards.
910
---
1011

1112
# Discover [discover]
1213

13-
You have questions about your data. What pages on your website contain a specific word or phrase? What events were logged most recently? What processes take longer than 500 milliseconds to respond?
14-
15-
$$$save-your-search$$$
16-
With **Discover**, you can quickly search and filter your data, get information about the structure of the fields, and display your findings in a visualization. You can also customize and save your Discover sessions and place them on a dashboard.
14+
**Discover** is the primary tool for exploring your {{product.elasticsearch}} data in {{product.kibana}}. Search and filter documents, analyze field structures, visualize patterns, and save findings to reuse later or share with dashboards. Whether investigating issues, analyzing trends, or validating data quality, **Discover** offers a flexible interface for understanding your data.
1715

1816
:::{image} /explore-analyze/images/kibana-hello-field.png
1917
:alt: A view of the Discover app
2018
:screenshot:
2119
:::
2220

21+
## What you can do with Discover
22+
23+
**Search and explore**
24+
: Search through your data using KQL, Lucene, or {{esql}}. Filter results to focus on what matters. Discover adapts its interface based on the type of data you're exploring, providing specialized experiences for logs, metrics, and other data types.
25+
26+
**Analyze fields and documents**
27+
: View field statistics, examine individual documents, compare multiple documents side by side, and find patterns in your log data.
28+
29+
**Visualize on the fly**
30+
: Create quick visualizations from aggregatable fields, or use {{esql}} to build charts directly from your queries.
31+
32+
**Save and share**
33+
: Save your Discover sessions to reuse later, add them to dashboards, or share them with your team. You can also generate reports and create alerts based on your searches.
34+
35+
## Get started
36+
37+
New to Discover? Start with these resources:
38+
39+
* **[Get started with Discover](discover/discover-get-started.md)** - A hands-on tutorial that walks you through exploring data, from loading data to filtering and visualizing your findings.
40+
* **[Using {{esql}}](discover/try-esql.md)** - Learn how to use the {{es}} Query Language for powerful data exploration.
41+
42+
## Common tasks
43+
44+
Once you're familiar with the basics, explore these guides for specific tasks:
45+
46+
* **[Search and filter data](discover/discover-get-started.md)** - Build queries and apply filters to narrow down your results.
47+
* **[Customize the Discover view](discover/document-explorer.md)** - Adjust the layout, columns, and display options to suit your needs.
48+
* **[Save a search for reuse](discover/save-open-search.md)** - Save your Discover sessions and add them to dashboards.
49+
50+
## Advanced features
51+
52+
The following guides cover additional features you can use in Discover:
53+
54+
* [Add runtime fields to your {{data-source}}](discover/discover-get-started.md#add-field-in-discover)
55+
* [Run queries in the background](discover/background-search.md)
56+
* [Analyze field statistics and patterns](discover/run-pattern-analysis-discover.md)
57+
* [Search for relevance](discover/discover-search-for-relevance.md)

explore-analyze/discover/background-search.md

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -7,23 +7,19 @@ applies_to:
77
serverless: unavailable
88
products:
99
- id: kibana
10-
description: Send your long-running queries to run in the background with background searches and search sessions, and focus on your other tasks while they complete.
10+
description: Send long-running queries to run in the background with background searches from Discover and Dashboards. Continue working while queries complete and access results later.
1111
---
1212

13-
# Run Discover and Dashboards queries in the background
13+
# Run Discover and Dashboards queries in the background [background-search]
14+
15+
Send long-running searches to run asynchronously while you continue working in {{product.kibana}}. Access your completed searches later from **Discover** or **Dashboards**, and manage all background searches from the toolbar.
1416

1517
::::{important} - Background search replaces Search sessions
1618

1719
Background search is a feature introduced in version 9.2. It replaces the deprecated **Search sessions** feature.
1820
If you have been using search sessions and upgrade to 9.2, your search sessions aren't lost and become background searches.
1921
::::
2022

21-
Sometimes you might need to search through large amounts of data, no matter how long the search takes. Consider a threat hunting scenario, where you need to search through years of data.
22-
23-
You can send your long-running searches to the background from **Discover** or **Dashboards** and let them run while you continue your work.
24-
25-
You can access your list of background searches at any time to check their status and manage them from the {icon}`background_task` **Background searches** button in the toolbar.
26-
2723
![Send search to background](https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/bltee31dcf0d3917c75/68ecf412e5bae49d65a286ff/background-search.gif " =75%")
2824

2925

@@ -51,7 +47,7 @@ To send searches to the background, and to view and interact with the list of ba
5147
:sync: 91
5248
In versions 9.1 and earlier, this feature is named **Search sessions**.
5349
* To save a session, you must have permissions for **Discover** and **Dashboard**, and the [Search sessions subfeature](../../deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md#kibana-feature-privileges).
54-
* To view and restore a saved session, you must have access to **Stack Management**.
50+
* To view and restore a saved session, you must have access to {{stack-manage-app}}.
5551
::::
5652

5753
:::::

explore-analyze/discover/discover-get-started.md

Lines changed: 2 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -6,21 +6,12 @@ applies_to:
66
serverless: ga
77
products:
88
- id: kibana
9+
description: Step-by-step tutorial for exploring data with Discover by selecting data views, filtering documents, analyzing fields, and creating visualizations using sample or your own data.
910
---
1011

1112
# Explore fields and data with Discover [discover-get-started]
1213

13-
Learn how to use **Discover** to:
14-
15-
* **Select** and **filter** your {{es}} data.
16-
* **Explore** the fields and content of your data in depth.
17-
* **Present** your findings in a visualization.
18-
19-
**Prerequisites:**
20-
21-
* If you don’t already have {{kib}}, [start a free trial](https://www.elastic.co/cloud/elasticsearch-service/signup?baymax=docs-body&elektra=docs) on Elastic Cloud.
22-
* You must have data in {{es}}. Examples on this page use the [ecommerce sample data set](../index.md#gs-get-data-into-kibana), but you can use your own data.
23-
* You should have an understanding of [{{es}} documents and indices](../../manage-data/data-store/index-basics.md).
14+
Learn how to explore your {{product.elasticsearch}} data using **Discover**. This tutorial walks you through selecting {{data-sources}}, filtering documents, analyzing field structures, and creating visualizations from your data.
2415

2516
## Context-aware data exploration [context-aware-discover]
2617

explore-analyze/discover/discover-search-for-relevance.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,14 @@ applies_to:
66
serverless: ga
77
products:
88
- id: kibana
9+
description: Sort search results by relevance score in Discover to identify the documents that best match your query. Use the score field to prioritize the most relevant data.
910
---
1011

1112
# Search for relevance [discover-search-for-relevance]
1213

13-
{{es}} assigns a relevancy, or score to each document, so you can can narrow your search to the documents with the most relevant results. The higher the score, the better it matches your query.
14+
{{product.elasticsearch}} assigns a relevancy score to each document based on how well it matches your query. Sorting by this score helps you identify the most relevant results quickly. This guide shows how to use **Discover** to sort documents by relevance score, putting the best matches at the top of your results.
1415

15-
This example shows how to use **Discover** to list your documents from most relevant to least relevant. This example uses the [sample flights data set](../index.md#gs-get-data-into-kibana), or you can use your own data.
16+
This example uses the [sample flights data set](../index.md#gs-get-data-into-kibana), or you can use your own data.
1617

1718
1. In **Discover**, open the {{data-source}} dropdown, and select the data that you want to work with.
1819

explore-analyze/discover/document-explorer.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,12 @@ applies_to:
66
serverless: ga
77
products:
88
- id: kibana
9+
description: Customize the Discover view with flexible display options for the document table, chart, and sidebar. Adjust columns, density, row height, and field visibility for optimal exploration.
910
---
1011

1112
# Customize the Discover view [document-explorer]
1213

13-
Fine tune your explorations by customizing **Discover** to bring out the the best view of your documents.
14+
**Discover** offers flexible customization options to optimize your data exploration experience. Adjust the document table layout, modify column arrangements, control chart and sidebar visibility, and configure display density to focus on the data that matters most. These customizations persist across sessions and help you work more efficiently with your {{product.elasticsearch}} data.
1415

1516
:::{tip}
1617
Discover provides default [context-aware experiences](/explore-analyze/discover/discover-get-started.md#context-aware-discover) tailored to the type of data that you're exploring, and you can further customize your Discover view on top of them.

explore-analyze/discover/run-pattern-analysis-discover.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,15 +6,14 @@ applies_to:
66
serverless: ga
77
products:
88
- id: kibana
9+
description: Detect patterns in unstructured data with pattern analysis in Discover. Categorize log messages, identify common structures, and filter noise during troubleshooting.
910
---
1011

1112
# Run a pattern analysis on your log data [run-pattern-analysis-discover]
1213

13-
Log pattern analysis helps you to find patterns in unstructured log messages and makes it easier to examine your data. It performs categorization analysis on a selected field of a {{data-source}}, creates categories based on the data and displays them together with a chart that shows the distribution of each category and an example document that matches the category.
14+
Pattern analysis in **Discover** helps you find patterns in unstructured log messages by performing categorization analysis on text fields. It creates categories based on message structures, displays their distribution in a chart, and provides example documents for each pattern. This makes it easier to identify common log patterns, filter out noise, and focus on anomalous messages during troubleshooting.
1415

15-
Log pattern analysis works on every text field.
16-
17-
This example uses the [sample web logs data](../index.md#gs-get-data-into-kibana), or you can use your own data.
16+
Pattern analysis works on any text field. This example uses the [sample web logs data](../index.md#gs-get-data-into-kibana), or you can use your own log data.
1817

1918
1. Go to **Discover**.
2019
2. Expand the {{data-source}} dropdown, and select **Kibana Sample Data Logs**.

explore-analyze/discover/save-open-search.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,19 +7,24 @@ applies_to:
77
serverless: ga
88
products:
99
- id: kibana
10+
description: Save Discover sessions to reuse searches, queries, and configured views. Add saved searches to dashboards or use them as a foundation for building visualizations.
1011
---
1112

12-
# Discover sessions: Save a search for reuse [save-open-search]
13+
# Save a search for reuse [save-open-search]
1314

14-
A saved Discover session is a convenient way to reuse a search that you’ve created in **Discover**. Discover sessions are good for saving a configured view of Discover to use later or adding search results to a dashboard, and can also serve as a foundation for building visualizations.
15+
Saved **Discover** sessions preserve your queries, filters, column selections, and view configurations for reuse. Save sessions to return to specific data explorations, share search results with team members, add searches to dashboards, or use them as a foundation for building visualizations. This guide shows how to save, reopen, duplicate, and manage Discover sessions.
1516

17+
## Requirements [save-search-requirements]
1618

17-
## Read-only access [discover-read-only-access]
19+
To save searches, you need **Create** and **Edit** permissions for the {{saved-objects-app}} feature in {{product.kibana}}. If you don't have these permissions, the **Save** button won't be visible. For more information, refer to [Read-only access](#discover-read-only-access).
20+
21+
22+
### Read-only access [discover-read-only-access]
1823

1924
If you don’t have sufficient privileges to save Discover sessions, the following indicator is displayed and the **Save** button is not visible. For more information, refer to [Granting access to {{kib}}](elasticsearch://reference/elasticsearch/roles.md).
2025

2126
:::{image} /explore-analyze/images/kibana-read-only-badge.png
22-
:alt: Example of Discover's read only access indicator in Kibana's header
27+
:alt: Example of Discover's read only access indicator in the {{product.kibana}} header
2328
:screenshot:
2429
:::
2530

0 commit comments

Comments
 (0)