You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: explore-analyze/dashboards/drilldowns.md
+18-17Lines changed: 18 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,18 +45,20 @@ The panels you create using the following editors support dashboard drilldowns:
45
45
Use the [**Sample web logs**](../index.md#gs-get-data-into-kibana) data to create a dashboard and add panels, then set a search and filter on the **[Logs] Web Traffic** dashboard.
46
46
47
47
1. Add the **Sample web logs** data.
48
-
2. Create a new dashboard, click **Add from Library**, then add the following panels:
48
+
2. Create a new dashboard.
49
49
50
-
***[Logs] Response Codes Over Time + Annotations**
51
-
***[Logs] Visits**
50
+
*{applies_to}`stack: ga 9.2` Select **Add** > **From library** in the toolbar.
51
+
*{applies_to}`stack: ga 9.0` Click **Add from library** in the dashboard toolbar.
52
52
53
-
3. Set the [time filter](../query-filter/filtering.md) to **Last 30 days**.
54
-
4. Save the dashboard. In the **Title** field, enter `Detailed logs`.
55
-
5. Open the **[Logs] Web Traffic** dashboard, then set a search and filter.
53
+
3. Add the following panel:
56
54
57
-
Search: `extension.keyword: ("gz" or "css" or "deb")`<br> Filter: `geo.src: US`
55
+
***[Logs] Visits**
58
56
57
+
4. Set the [time filter](../query-filter/filtering.md) to **Last 30 days**.
58
+
5. Save the dashboard. In the **Title** field, enter `Detailed logs`.
59
+
6. Open the **[Logs] Web Traffic** dashboard, then set a search and filter.
59
60
61
+
Search: `extension.keyword: ("gz" or "css" or "deb")`<br> Filter: `geo.src: US`
60
62
61
63
### Create the dashboard drilldown [_create_the_dashboard_drilldown]
62
64
@@ -77,8 +79,6 @@ Create a drilldown that opens the **Detailed logs** dashboard from the **[Logs]
77
79
:screenshot:
78
80
:::
79
81
80
-
81
-
82
82
## Create URL drilldowns [create-url-drilldowns]
83
83
84
84
URL drilldowns enable you to navigate from a dashboard to external websites. Destination URLs can be dynamic, depending on the dashboard context or user interaction with a panel. To create URL drilldowns, you add [variables](/explore-analyze/dashboards/drilldowns.md) to a URL template, which configures the behavior of the drilldown. All panels that you create with the visualization editors support dashboard drilldowns.
@@ -92,22 +92,23 @@ Some panels support multiple interactions, also known as triggers. The [variable
92
92
93
93
For example, **Single click** has `{{event.value}}` and **Range selection** has `{{event.from}}` and `{{event.to}}`.
94
94
95
-
96
95
### Create a URL drilldown [_create_a_url_drilldown]
97
96
98
97
For example, if you have a dashboard that shows data from a Github repository, you can create a URL drilldown that opens Github from the dashboard panel.
99
98
100
99
1. Add the [**Sample web logs**](../index.md#gs-get-data-into-kibana) data.
101
100
2. Open the **[Logs] Web Traffic** dashboard.
102
101
3. In the toolbar, click **Edit**.
103
-
4. Create a donut chart
102
+
4. Create a pie chart.
103
+
104
+
* {applies_to}`stack: ga 9.2` Select **Add** > **Visualization** in the toolbar.
105
+
* {applies_to}`stack: ga 9.0` Click **Create visualization** in the dashboard toolbar.
104
106
105
-
1. Click **Create visualization**.
106
-
2. From the **Chart type** dropdown, select **Donut**.
107
-
3. From the **Available fields** list, drag **machine.os.keyword** to the workspace.
108
-
4. Click **Save and return**.
107
+
2. From the **Chart type** dropdown, select **Pie**.
108
+
3. From the **Available fields** list, drag **machine.os.keyword** to the workspace.
109
+
4. Click **Save and return**.
109
110
110
-
5. Open the donut chart panel menu, then select **Create drilldown**.
111
+
5. Open the pie chart panel menu, then select **Create drilldown**.
111
112
6. Click **Go to URL**.
112
113
113
114
1. Give the drilldown a name. For example, `Show on Github`.
@@ -123,7 +124,7 @@ For example, if you have a dashboard that shows data from a Github repository, y
123
124
4. Click **Create drilldown**.
124
125
125
126
7. Save the dashboard.
126
-
8. On the donut chart panel, click any chart slice, thenselect**Show on Github**.
127
+
8. On the pie chart panel, click any chart slice, thenselect**Show on Github**.
Copy file name to clipboardExpand all lines: explore-analyze/dashboards/open-dashboard.md
+5-12Lines changed: 5 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,32 +17,25 @@ products:
17
17
When looking for a specific dashboard, you can filter them by tag or by creator, or search the list based on their name and description. Note that the creator information is only available for dashboards created on or after version 8.14.
18
18
::::
19
19
20
-
3. Click the dashboard **Title** you want to open.
21
-
4. Make sure that you are in **Edit** mode to be able to make changes to the dashboard. You can switch between **Edit** and **View** modes from the toolbar.
22
-
20
+
3. Click the dashboard name you want to open.
21
+
The dashboard opens automatically in **Edit** mode if you have the right permissions. You can switch between edit and view modes from the toolbar.
23
22
24
23
5. Make the changes that you need to the dashboard:
25
24
26
25
* Adjust the dashboard’s settings
27
26
*[Add, remove, move, or edit panels](../visualize.md#panels-editors)
28
27
*[Change the available controls](add-controls.md)
29
28
30
-
6.**Save** the dashboard. You automatically switch to **View** mode upon saving.
29
+
6.**Save** the dashboard.
31
30
32
31
::::{note}
33
32
Managed dashboards can’t be edited directly, but you can [duplicate](duplicate-dashboards.md) them and edit these duplicates.
34
33
::::
35
34
36
-
37
35
## Reset dashboard changes [reset-the-dashboard]
38
36
39
-
When editing a dashboard, you can revert any changes you’ve made since the last save using **Reset dashboards**.
37
+
When editing a dashboard, you can revert any changes you’ve made since the last save using the **Reset** button in the toolbar.
40
38
41
39
::::{note}
42
40
Once changes are saved, you can no longer revert them in one click, and instead have to edit the dashboard manually.
43
-
::::
44
-
45
-
46
-
1. In the toolbar, click **Reset**.
47
-
2. On the **Reset dashboard?** window, click **Reset dashboard**.
48
-
Copy file name to clipboardExpand all lines: explore-analyze/discover/discover-get-started.md
+36-1Lines changed: 36 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,6 +94,8 @@ You can later filter the data that shows in the chart and in the table by specif
94
94
You can combine multiple keywords or characters. For example, `geo dest` finds `geo.dest` and `geo.src.dest`.
95
95
::::
96
96
97
+
{applies_to}`stack: ga 9.2` For some searches, Discover suggests recommended fields to explore. These suggestions are based on the data you query and are managed by Elastic.
98
+
97
99
2. Select a field to view its most frequent values.
98
100
**Discover** shows the top 10 values and the number of records used to calculate those values.
99
101
@@ -303,6 +305,39 @@ Note that in ES|QL mode, the **Documents** tab is named **Results**.
Copy file name to clipboardExpand all lines: solutions/search/agent-builder/limitations-known-issues.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,6 +42,12 @@ Error: Invalid function call syntax
42
42
Error executing agent: No tool calls found in the response.
43
43
```
44
44
45
+
### {{esql}} limitations
46
+
47
+
{{esql}} tools are subject to the current limitations of the {{esql}} language itself. For example, [named parameters](elasticsearch://reference/query-languages/esql/esql-syntax.md#esql-function-named-params) (`?parameter_name`) do not currently work with the `LIKE` and `RLIKE` operators ([issue #131356](https://github.com/elastic/elasticsearch/issues/131356)).
48
+
49
+
For a complete list of {{esql}} limitations, refer to the the [{{esql}} limitations documentation](elasticsearch://reference/query-languages/esql/limitations.md).
50
+
45
51
### Misinterpreted SQL syntax as ES|QL
46
52
47
53
The `.execute_esql` tool is designed only for [{{esql}}](elasticsearch://reference/query-languages/esql.md) syntax, not other query languages.
Copy file name to clipboardExpand all lines: solutions/search/agent-builder/tools/esql-tools.md
+22-1Lines changed: 22 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,13 +52,34 @@ Parameters can be configured as:
52
52
53
53
In your {{esql}} query, reference parameters using the `?parameter_name` syntax. The agent will automatically interpolate parameter values when executing the query.
54
54
55
+
### Example
56
+
57
+
Here's an example {{esql}} tool that searches for books using full-text search. `?search_terms` is a named parameter that the agent will provide when executing the query.
58
+
59
+
```esql
60
+
FROM books
61
+
| WHERE MATCH(title, ?search_terms)
62
+
| KEEP title, author, year
63
+
| LIMIT 10
64
+
```
65
+
66
+
You can ask the LLM to infer the parameters for the query or add them manually.
67
+
68
+
:::{image} ../images/create-esql-tool-query.png
69
+
:alt: Creating an ES|QL tool with a parameterized query
-**Use meaningful parameter names**: Choose names that clearly indicate what the parameter represents (e.g., `start_date` instead of `date1`)
76
+
-**Define parameter types**: Ensure parameters have the correct type to avoid runtime errors
60
77
-**Provide clear descriptions**: Help agents understand when and how to use each parameter
61
78
79
+
## Limitations
80
+
81
+
{{esql}} tools are subject to the current limitations of the {{esql}} language itself. For more information, refer to [{{esql}} tool limitations](../limitations-known-issues.md#esql-limitations).
82
+
62
83
## {{esql}} documentation
63
84
64
85
To learn more about the language, refer to the [{{esql}} docs](elasticsearch://reference/query-languages/esql.md).
0 commit comments