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: deploy-manage/cloud-organization/tools-and-apis.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,8 @@ You can use the [{{ecloud}} API](https://www.elastic.co/docs/api/doc/cloud/) to
13
13
* Refer to [](/deploy-manage/api-keys/elastic-cloud-api-keys.md) to learn how to generate an API key to access this API.
14
14
* Refer to [{{ecloud}} RESTful API](cloud://reference/cloud-hosted/ec-api-restful.md) for usage information and examples.
15
15
16
+
For additional billing and cost information for {{ecloud}}, you can use the [Cloud Billing API](https://www.elastic.co/docs/api/doc/cloud-billing/).
17
+
16
18
For {{ecloud}} [service status](/deploy-manage/cloud-organization/service-status.md) updates, you can use the [Service Status API](https://status.elastic.co/api/).
17
19
18
20
For information about all of the tools and APIs that you can use to manage your {{ech}} deployments and {{serverless-full}} projects, refer to [](/deploy-manage/deploy/elastic-cloud/tools-apis.md).
Copy file name to clipboardExpand all lines: deploy-manage/deploy/elastic-cloud/tools-apis.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,7 @@ The following REST APIs allow you to manage your {{ecloud}} organization, users,
33
33
| {{ecloud}} organization<br><br>{{ech}} deployments |[{{ecloud}} API](https://www.elastic.co/docs/api/doc/cloud/)| Manage your Cloud organization, members, costs, billing, and more.<br><br>Manage your hosted deployments and all of the resources associated with them, including scaling or autoscaling resources, and managing network security, deployment extensions, remote clusters, and {{stack}} versions.<br><br>Refer to [{{ecloud}} RESTful API](cloud://reference/cloud-hosted/ec-api-restful.md) for usage information and examples. |
| {{ecloud}} billing information |[Cloud Billing API](https://www.elastic.co/docs/api/doc/cloud-billing/)| Retrieve additional billing and cost information about your {{ecloud}} organization. |
36
37
37
38
38
39
### APIs to interact with data and solution features
Copy file name to clipboardExpand all lines: deploy-manage/security/private-connectivity-aws.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -301,7 +301,7 @@ If the policy doesn't contain a VPC filter, then the association can serve as a
301
301
302
302
## Access the deployment over a PrivateLink [ec-access-the-deployment-over-private-link]
303
303
304
-
For traffic to connect with the deployment over Azure PrivateLink, the client making the request needs to be located within the VPC where you’ve created the VPC endpoint. You can also set up network traffic to flow through the originating VPC from somewhere else, such as another VPC or VPN from your corporate network. This assumes that the VPC endpoint and the DNS record are also available within that context. Check your service provider documentation for setup instructions.
304
+
For traffic to connect with the deployment over AWS PrivateLink, the client making the request needs to be located within the VPC where you’ve created the VPC endpoint. You can also set up network traffic to flow through the originating VPC from somewhere else, such as another VPC or VPN from your corporate network. This assumes that the VPC endpoint and the DNS record are also available within that context. Check your service provider documentation for setup instructions.
305
305
306
306
::::{important}
307
307
Use the alias you’ve set up as CNAME DNS record to access your deployment.
@@ -408,4 +408,4 @@ To delete a policy:
408
408
409
409
:::{include} _snippets/network-security-page.md
410
410
:::
411
-
4. Find the policy you want to edit, then click the **Delete** icon. The icon is inactive if there are deployments associated with the policy.
411
+
4. Find the policy you want to edit, then click the **Delete** icon. The icon is inactive if there are deployments associated with the policy.
To add a Discover query to a dashboard in a way that preserves the [controls created from Discover](/explore-analyze/discover/try-esql.md#add-variable-control-discover) and also adds them to the dashboard, do as follows:
2
+
3
+
1. Save the {{esql}} query containing the variable control into a Discover session. If your Discover session contains several tabs, only the first tab will be imported to the dashboard.
4
+
5
+
1. Go to **Dashboards** and open or create one.
6
+
7
+
1. Select **Add**, then **From library**.
8
+
9
+
1. Find and select the Discover session you saved earlier.
10
+
11
+
A new panel appears on the dashboard with the results of the query along with any attached controls.
12
+
13
+

14
+
15
+
:::{note}
16
+
When you add a visualization to a dashboard using the {icon}`save`**Save visualization** option, controls are not added to the dashboard.
* For controls with **Static values**, enter available controls manually or select them from the dropdown list.
3
+
* For controls with **Values from a query**, write an {{esql}} query to populate the list of options.
4
+
* The name of the control. This name is used to reference the control in {{esql}} queries.
5
+
* Start the name with `?` if you want the options to be simple static values.
6
+
* {applies_to}`stack: ga 9.1` Start the name with `??` if you want the options to be fields or functions.
7
+
* The values users can select for this control. You can add multiple values from suggested fields, or type in custom values. If you selected **Values from a query**, you must instead write an {{esql}} query at this step.
8
+
* The label of the control. This is the label displayed in **Discover** or in the dashboard.
9
+
* The width of the control.
10
+
11
+

Copy file name to clipboardExpand all lines: explore-analyze/alerts-cases/watcher/schedule-types.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -422,7 +422,7 @@ By default, the `yearly` schedule is evaluated in the UTC time zone. To use a di
422
422
## {{watcher}} cron schedule [schedule-cron]
423
423
424
424
425
-
Defines a [`schedule`](trigger-schedule.md) using a [cron expression](elasticsearch://reference/elasticsearch/rest-apis/api-conventions.md#api-cron-expressions) that specifiues when to execute a watch.
425
+
Defines a [`schedule`](trigger-schedule.md) using a [cron expression](elasticsearch://reference/elasticsearch/rest-apis/api-conventions.md#api-cron-expressions) that specifies when to execute a watch.
426
426
427
427
::::{tip}
428
428
While cron expressions are powerful, a regularly occurring schedule is easier to configure with the other schedule types. If you must use a cron schedule, make sure you verify it with [`elasticsearch-croneval`](elasticsearch://reference/elasticsearch/command-line-tools/elasticsearch-croneval.md) .
Copy file name to clipboardExpand all lines: explore-analyze/dashboards/add-controls.md
+16-36Lines changed: 16 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,6 +90,10 @@ You can add one interactive time slider control to a dashboard.
90
90
91
91
92
92
## Add variable controls [add-variable-control]
93
+
```{applies_to}
94
+
stack: preview 9.0
95
+
serverless: preview
96
+
```
93
97
94
98
:::{note}
95
99
In versions `9.0` and `9.1`, variable controls are called {{esql}} controls.
@@ -113,17 +117,8 @@ Only **Options lists** are supported for {{esql}}-based controls. Options can be
113
117
114
118
2. A menu opens to let you configure the control. This is where you can specify:
115
119
116
-
* The type of the control.
117
-
* For controls with **Static values**, select the options available in the controls by entering them manually or by using a dropdown listing available values.
118
-
* For controls with **Values from a query**, write an {{esql}} query to populate the list of options.
119
-
* The name of the control. This name is used to reference the control in {{esql}} queries.
120
-
* Start the name with `?` if you want the options to be simple static values.
121
-
* Start the name with `??` if you want the options of the control to be fields or functions. {applies_to}`stack: ga 9.1`
122
-
* The values users can select for this control. You can add multiple values from suggested fields, or type in custom values. If you selected **Values from a query**, you must instead write an {{esql}} query at this step.
123
-
* The label of the control. This is the label displayed for users viewing the dashboard for that control.
124
-
* The width of the control.
125
-
126
-

* Integrate filtering into your {{esql}} experience
139
-
140
-
```esql
141
-
| WHERE field == ?value
142
-
```
143
-
144
-
* Fields in controls for dynamic group by
145
-
146
-
```esql
147
-
| STATS count=COUNT(*) BY ?field
148
-
```
149
-
150
-
* Variable time ranges? Bind function configuration settings to a control
151
-
152
-
```esql
153
-
| BUCKET(@timestamp, ?interval),
154
-
```
155
-
156
-
* Make the function itself dynamic
133
+

157
134
158
-
```esql
159
-
| STATS metric = ?function
160
-
```
135
+
### Import a Discover query along with its controls into a dashboard
136
+
```{applies_to}
137
+
stack: preview 9.2
138
+
serverless: preview
139
+
```
161
140
162
-

0 commit comments