diff --git a/deploy-manage/deploy/elastic-cloud/create-serverless-project.md b/deploy-manage/deploy/elastic-cloud/create-serverless-project.md index a3ed45d3c6..3a29622d2c 100644 --- a/deploy-manage/deploy/elastic-cloud/create-serverless-project.md +++ b/deploy-manage/deploy/elastic-cloud/create-serverless-project.md @@ -15,8 +15,8 @@ Choose the type of project that matches your needs and we’ll help you get star | | | | --- | --- | | | | -| ![elasticsearch](https://www.elastic.co/docs/assets/images/serverless-elasticsearch.png "") | Elasticsearch
Build custom search applications with Elasticsearch.

[**View guide →**](../../../solutions/search.md)
| -| ![observability](https://www.elastic.co/docs/assets/images/serverless-observability.png "") | Observability
Monitor applications and systems with Elastic Observability.

[**View guide →**](../../../solutions/observability.md)
| -| ![security](https://www.elastic.co/docs/assets/images/serverless-security.png "") | Security
Detect, investigate, and respond to threats with Elastic Security.

[**View guide →**](../../../solutions/security/elastic-security-serverless.md)
| +| ![elasticsearch](https://www.elastic.co/docs/assets/images/elasticsearch.png "") | Elasticsearch
Build custom search applications with Elasticsearch.

[**View guide →**](../../../solutions/search.md)
| +| ![observability](https://www.elastic.co/docs/assets/images/observability.png "") | Observability
Monitor applications and systems with Elastic Observability.

[**View guide →**](../../../solutions/observability.md)
| +| ![security](https://www.elastic.co/docs/assets/images/security.png "") | Security
Detect, investigate, and respond to threats with Elastic Security.

[**View guide →**](../../../solutions/security/elastic-security-serverless.md)
| | | | diff --git a/deploy-manage/remote-clusters/ec-migrate-ccs.md b/deploy-manage/remote-clusters/ec-migrate-ccs.md index 5eca7158f9..f1f18d0009 100644 --- a/deploy-manage/remote-clusters/ec-migrate-ccs.md +++ b/deploy-manage/remote-clusters/ec-migrate-ccs.md @@ -21,7 +21,7 @@ You can use a PUT request to update your deployment, changing both the deploymen You can also find the template in the [list of templates available for each region](https://www.elastic.co/guide/en/cloud/current/ec-regions-templates-instances.html). - :::{image} images/cloud-ec-migrate-deployment-template(2).png + :::{image} ../../images/cloud-ec-migrate-deployment-template(2).png :alt: Deployment Template ID :class: screenshot ::: diff --git a/explore-analyze/alerts-cases/alerts/rule-type-index-threshold.md b/explore-analyze/alerts-cases/alerts/rule-type-index-threshold.md index e440d8f5d8..b9ba2562c3 100644 --- a/explore-analyze/alerts-cases/alerts/rule-type-index-threshold.md +++ b/explore-analyze/alerts-cases/alerts/rule-type-index-threshold.md @@ -135,7 +135,7 @@ In this example, you will use the {{kib}} [sample weblog data set](https://www.e You can add one or more actions to your rule to generate notifications when its conditions are met and when they are no longer met. For each action, you must select a connector, set the action frequency, and compose the notification details. For example, add an action that uses a server log connector to write an entry to the Kibana server log: - :::{image} ../../../images/rule-types-index-threshold-example-action.png + :::{image} ../../../images/kibana-rule-types-index-threshold-example-action.png :alt: Add an action to the rule :class: screenshot ::: diff --git a/explore-analyze/alerts-cases/watcher/actions-slack.md b/explore-analyze/alerts-cases/watcher/actions-slack.md index 5715b870be..a6583fab34 100644 --- a/explore-analyze/alerts-cases/watcher/actions-slack.md +++ b/explore-analyze/alerts-cases/watcher/actions-slack.md @@ -152,7 +152,7 @@ To configure a Slack account, at a minimum you need to specify the account name bin/elasticsearch-keystore add xpack.notification.slack.account.monitoring.secure_url ``` -::::{warning} +::::{warning} You can no longer configure Slack accounts using `elasticsearch.yml` settings. Please use {{es}}'s secure [keystore](../../../deploy-manage/security/secure-settings.md) method instead. :::: @@ -167,7 +167,7 @@ xpack.notification.slack: message_defaults: from: x-pack to: notifications - icon: http://example.com/images/elasticsearch-reference-watcher-icon.jpg + icon: http://example.com/images/watcher-icon.jpg attachment: fallback: "X-Pack Notification" color: "#36a64f" diff --git a/explore-analyze/dashboards/add-controls.md b/explore-analyze/dashboards/add-controls.md index 77177bcd99..e7c1e69f8a 100644 --- a/explore-analyze/dashboards/add-controls.md +++ b/explore-analyze/dashboards/add-controls.md @@ -45,7 +45,7 @@ To add interactive Options list and Range slider controls, create the controls, 1. Open or create a new dashboard. 2. In **Edit** mode, select **Controls** > **Add control** in the dashboard toolbar. - :::{image} images/dashboard-add-control-8.15.0.png + :::{image} ../../images/kibana-dashboard-add-control-8.15.0.png :alt: Controls button in the toolbar with the Add Control option selected :class: screenshot ::: @@ -95,7 +95,7 @@ You can add one interactive time slider control to a dashboard. 1. Open or create a new dashboard. 2. In **Edit** mode, select **Controls** > **Add time slider control**. - :::{image} images/dashboard-add-time-slider-control-8.15.0.png + :::{image} ../../images/kibana-dashboard-add-time-slider-control-8.15.0.png :alt: Controls button in the toolbar with the Add a time slider option selected :class: screenshot ::: @@ -110,7 +110,7 @@ Several settings that apply to all controls of the same dashboard are available. 1. In **Edit** mode, select **Controls** > **Settings**. - :::{image} images/dashboard-controls-settings-8.15.0.png + :::{image} ../../images/kibana-dashboard-controls-settings-8.15.0.png :alt: Controls button in the toolbar with the Settings option selected :class: screenshot ::: diff --git a/explore-analyze/dashboards/create-dashboard-of-panels-with-web-server-data.md b/explore-analyze/dashboards/create-dashboard-of-panels-with-web-server-data.md index a3723dca95..b7fb8026f5 100644 --- a/explore-analyze/dashboards/create-dashboard-of-panels-with-web-server-data.md +++ b/explore-analyze/dashboards/create-dashboard-of-panels-with-web-server-data.md @@ -64,14 +64,14 @@ The only number function that you can use with **clientip** is **Unique count**, 1. Open the **Visualization type** dropdown, then select **Metric**. - :::{image} images/visualization-type-dropdown-8.16.0.png + :::{image} ../../images/kibana-visualization-type-dropdown-8.16.0.png :alt: Visualization type dropdown :class: screenshot ::: 2. From the **Available fields** list, drag **clientip** to the workspace or layer pane. - :::{image} images/tutorial-unique-count-of-client-ip-8.16.0.png + :::{image} ../../images/kibana-tutorial-unique-count-of-client-ip-8.16.0.png :alt: Metric visualization of the clientip field :class: screenshot ::: @@ -123,14 +123,14 @@ To save space on the dashboard, hide the axis labels. 1. Open the **Left axis** menu, then select **None** from the **Axis title** dropdown. - :::{image} images/line-chart-left-axis-8.16.0.png + :::{image} ../../images/kibana-line-chart-left-axis-8.16.0.png :alt: Left axis menu :class: screenshot ::: 2. Open the **Bottom axis** menu, then select **None** from the **Axis title** dropdown. - :::{image} images/line-chart-bottom-axis-8.16.0.png + :::{image} ../../images/kibana-line-chart-bottom-axis-8.16.0.png :alt: Bottom axis menu :class: screenshot ::: @@ -162,7 +162,7 @@ The **Top values** function ranks the unique values of a field by another functi 3. Drag **request.keyword** to the workspace. - :::{image} images/tutorial-top-values-of-field-8.16.0.png + :::{image} ../../images/kibana-tutorial-top-values-of-field-8.16.0.png :alt: Vertical bar chart with top values of request.keyword by most unique visitors :class: screenshot ::: @@ -174,7 +174,7 @@ The chart labels are unable to display because the **request.keyword** field con 1. Open the **Visualization type** dropdown, then select **Table**. - :::{image} images/table-with-request-keyword-and-client-ip-8.16.0.png + :::{image} ../../images/kibana-table-with-request-keyword-and-client-ip-8.16.0.png :alt: Table with top values of request.keyword by most unique visitors :class: screenshot ::: diff --git a/explore-analyze/dashboards/create-dashboard.md b/explore-analyze/dashboards/create-dashboard.md index 1be1b20c90..3d3f53a9b9 100644 --- a/explore-analyze/dashboards/create-dashboard.md +++ b/explore-analyze/dashboards/create-dashboard.md @@ -17,7 +17,7 @@ mapped_pages: * **Add from library**. Select existing content that has already been configured and saved to the **Visualize Library**. * [**Controls**](add-controls.md). Add controls to help filter the content of your dashboard. - :::{image} images/add_content_to_dashboard_8.15.0.png + :::{image} ../../images/kibana-add_content_to_dashboard_8.15.0.png :alt: Options to add content to your dashboard :class: screenshot ::: diff --git a/explore-analyze/scripting/dissect.md b/explore-analyze/scripting/dissect.md index 282e82d893..57ca668de4 100644 --- a/explore-analyze/scripting/dissect.md +++ b/explore-analyze/scripting/dissect.md @@ -16,7 +16,7 @@ Dissect patterns are comprised of *variables* and *separators*. Anything defined For example, let’s say you have log data with a `message` field that looks like this: ```js -"message" : "247.37.0.0 - - [30/Apr/2020:14:31:22 -0500] \"GET /images/elasticsearch-reference-hm_nbg.jpg HTTP/1.0\" 304 0" +"message" : "247.37.0.0 - - [30/Apr/2020:14:31:22 -0500] \"GET /images/hm_nbg.jpg HTTP/1.0\" 304 0" ``` You assign variables to each part of the data to construct a successful dissect pattern. Remember, tell dissect *exactly* what you want you want to match on. @@ -157,7 +157,7 @@ After mapping the fields you want to retrieve, index a few records from your log ```console POST /my-index/_bulk?refresh=true {"index":{}} -{"timestamp":"2020-04-30T14:30:17-05:00","message":"40.135.0.0 - - [30/Apr/2020:14:30:17 -0500] \"GET /images/elasticsearch-reference-hm_bg.jpg HTTP/1.0\" 200 24736"} +{"timestamp":"2020-04-30T14:30:17-05:00","message":"40.135.0.0 - - [30/Apr/2020:14:30:17 -0500] \"GET /images/hm_bg.jpg HTTP/1.0\" 200 24736"} {"index":{}} {"timestamp":"2020-04-30T14:30:53-05:00","message":"232.0.0.0 - - [30/Apr/2020:14:30:53 -0500] \"GET /images/hm_bg.jpg HTTP/1.0\" 200 24736"} {"index":{}} diff --git a/explore-analyze/scripting/grok.md b/explore-analyze/scripting/grok.md index eb96a4df86..2da865c4dd 100644 --- a/explore-analyze/scripting/grok.md +++ b/explore-analyze/scripting/grok.md @@ -52,7 +52,7 @@ New features and enhancements will be added to the ECS-compliant files. The lega You can incorporate predefined grok patterns into Painless scripts to extract data. To test your script, use either the [field contexts](https://www.elastic.co/guide/en/elasticsearch/painless/current/painless-execute-api.html#painless-execute-runtime-field-context) of the Painless execute API or create a runtime field that includes the script. Runtime fields offer greater flexibility and accept multiple documents, but the Painless execute API is a great option if you don’t have write access on a cluster where you’re testing a script. -::::{tip} +::::{tip} If you need help building grok patterns to match your data, use the [Grok Debugger](../query-filter/tools/grok-debugger.md) tool in {{kib}}. :::: @@ -61,7 +61,7 @@ For example, if you’re working with Apache log data, you can use the `%{{COMMO ```js "timestamp":"2020-04-30T14:30:17-05:00","message":"40.135.0.0 - - -[30/Apr/2020:14:30:17 -0500] \"GET /images/elasticsearch-reference-hm_bg.jpg HTTP/1.0\" 200 24736" +[30/Apr/2020:14:30:17 -0500] \"GET /images/hm_bg.jpg HTTP/1.0\" 200 24736" ``` To extract the IP address from the `message` field, you can write a Painless script that incorporates the `%{{COMMONAPACHELOG}}` syntax. You can test this script using the [`ip` field context](https://www.elastic.co/guide/en/elasticsearch/painless/current/painless-execute-api.html#painless-runtime-ip) of the Painless execute API, but let’s use a runtime field instead. @@ -98,7 +98,7 @@ POST /my-index/_bulk?refresh {"index":{}} {"timestamp":"2020-04-30T14:31:19-05:00","message":"247.37.0.0 - - [30/Apr/2020:14:31:19 -0500] \"GET /french/splash_inet.html HTTP/1.0\" 200 3781"} {"index":{}} -{"timestamp":"2020-04-30T14:31:22-05:00","message":"247.37.0.0 - - [30/Apr/2020:14:31:22 -0500] \"GET /images/elasticsearch-reference-hm_nbg.jpg HTTP/1.0\" 304 0"} +{"timestamp":"2020-04-30T14:31:22-05:00","message":"247.37.0.0 - - [30/Apr/2020:14:31:22 -0500] \"GET /images/hm_nbg.jpg HTTP/1.0\" 304 0"} {"index":{}} {"timestamp":"2020-04-30T14:31:27-05:00","message":"252.0.0.0 - - [30/Apr/2020:14:31:27 -0500] \"GET /images/hm_bg.jpg HTTP/1.0\" 200 24736"} {"index":{}} diff --git a/explore-analyze/scripting/scripting-field-extraction.md b/explore-analyze/scripting/scripting-field-extraction.md index 0d106a02cd..d8437a9e71 100644 --- a/explore-analyze/scripting/scripting-field-extraction.md +++ b/explore-analyze/scripting/scripting-field-extraction.md @@ -36,7 +36,7 @@ After mapping the fields you want to retrieve, index a few records from your log ```console POST /my-index/_bulk?refresh {"index":{}} -{"timestamp":"2020-04-30T14:30:17-05:00","message":"40.135.0.0 - - [30/Apr/2020:14:30:17 -0500] \"GET /images/elasticsearch-reference-hm_bg.jpg HTTP/1.0\" 200 24736"} +{"timestamp":"2020-04-30T14:30:17-05:00","message":"40.135.0.0 - - [30/Apr/2020:14:30:17 -0500] \"GET /images/hm_bg.jpg HTTP/1.0\" 200 24736"} {"index":{}} {"timestamp":"2020-04-30T14:30:53-05:00","message":"232.0.0.0 - - [30/Apr/2020:14:30:53 -0500] \"GET /images/hm_bg.jpg HTTP/1.0\" 200 24736"} {"index":{}} @@ -44,7 +44,7 @@ POST /my-index/_bulk?refresh {"index":{}} {"timestamp":"2020-04-30T14:31:19-05:00","message":"247.37.0.0 - - [30/Apr/2020:14:31:19 -0500] \"GET /french/splash_inet.html HTTP/1.0\" 200 3781"} {"index":{}} -{"timestamp":"2020-04-30T14:31:22-05:00","message":"247.37.0.0 - - [30/Apr/2020:14:31:22 -0500] \"GET /images/elasticsearch-reference-hm_nbg.jpg HTTP/1.0\" 304 0"} +{"timestamp":"2020-04-30T14:31:22-05:00","message":"247.37.0.0 - - [30/Apr/2020:14:31:22 -0500] \"GET /images/hm_nbg.jpg HTTP/1.0\" 304 0"} {"index":{}} {"timestamp":"2020-04-30T14:31:27-05:00","message":"252.0.0.0 - - [30/Apr/2020:14:31:27 -0500] \"GET /images/hm_bg.jpg HTTP/1.0\" 200 24736"} {"index":{}} @@ -52,7 +52,7 @@ POST /my-index/_bulk?refresh ``` -## Extract an IP address from a log message (Grok) [field-extraction-ip] +## Extract an IP address from a log message (Grok) [field-extraction-ip] If you want to retrieve results that include `clientip`, you can add that field as a runtime field in the mapping. The following runtime script defines a grok pattern that extracts structured fields out of the `message` field. @@ -121,7 +121,7 @@ The response includes documents where the value for `http.clientip` matches `40. ``` -## Parse a string to extract part of a field (Dissect) [field-extraction-parse] +## Parse a string to extract part of a field (Dissect) [field-extraction-parse] Instead of matching on a log pattern like in the [previous example](#field-extraction-ip), you can just define a dissect pattern to include the parts of the string that you want to discard. @@ -193,7 +193,7 @@ The response includes a single document where the HTTP response is `304`: ``` -## Split values in a field by a separator (Dissect) [field-extraction-split] +## Split values in a field by a separator (Dissect) [field-extraction-split] Let’s say you want to extract part of a field like in the previous example, but you want to split on specific values. You can use a dissect pattern to extract only the information that you want, and also return that data in a specific format. diff --git a/explore-analyze/visualize/maps/maps-getting-started.md b/explore-analyze/visualize/maps/maps-getting-started.md index e9248e8051..4fa4130643 100644 --- a/explore-analyze/visualize/maps/maps-getting-started.md +++ b/explore-analyze/visualize/maps/maps-getting-started.md @@ -137,7 +137,7 @@ You’ll create a layer for [aggregated data](../../aggregations.md) and make it Your map will look like this between zoom levels 0 and 9: - :::{image} ../../../images/sample_data_web_logs.png + :::{image} ../../../images/kibana-sample_data_web_logs.png :alt: Map showing what zoom level 3 looks like :class: screenshot ::: diff --git a/images/cloud-ce-copy-remote-cluster-parameters.png b/images/cloud-ce-copy-remote-cluster-parameters.png new file mode 100644 index 0000000000..325cf37509 Binary files /dev/null and b/images/cloud-ce-copy-remote-cluster-parameters.png differ diff --git a/images/cloud-delete-trust-environment.png b/images/cloud-delete-trust-environment.png new file mode 100644 index 0000000000..a376e85672 Binary files /dev/null and b/images/cloud-delete-trust-environment.png differ diff --git a/images/cloud-ec-ce-autoscaling-data-summary2.png b/images/cloud-ec-ce-autoscaling-data-summary2.png new file mode 100644 index 0000000000..f650fdfb28 Binary files /dev/null and b/images/cloud-ec-ce-autoscaling-data-summary2.png differ diff --git a/images/cloud-ec-ce-autoscaling-ml-summary2.png b/images/cloud-ec-ce-autoscaling-ml-summary2.png new file mode 100644 index 0000000000..8380f8736d Binary files /dev/null and b/images/cloud-ec-ce-autoscaling-ml-summary2.png differ diff --git a/images/cloud-ec-create-deployment.png b/images/cloud-ec-create-deployment.png new file mode 100644 index 0000000000..58ee5e8caf Binary files /dev/null and b/images/cloud-ec-create-deployment.png differ diff --git a/images/cloud-ec-create-from-snapshot-updated.png b/images/cloud-ec-create-from-snapshot-updated.png new file mode 100644 index 0000000000..dbc7aacc01 Binary files /dev/null and b/images/cloud-ec-create-from-snapshot-updated.png differ diff --git a/images/cloud-ec-deployment-mainpage.png b/images/cloud-ec-deployment-mainpage.png new file mode 100644 index 0000000000..10aa5cdf74 Binary files /dev/null and b/images/cloud-ec-deployment-mainpage.png differ diff --git a/images/cloud-ec-login-first-deployment.png b/images/cloud-ec-login-first-deployment.png new file mode 100644 index 0000000000..b269169d75 Binary files /dev/null and b/images/cloud-ec-login-first-deployment.png differ diff --git a/images/cloud-ec-marketplace-azure-traffic-filter-option.png b/images/cloud-ec-marketplace-azure-traffic-filter-option.png new file mode 100644 index 0000000000..ca20c034cd Binary files /dev/null and b/images/cloud-ec-marketplace-azure-traffic-filter-option.png differ diff --git a/images/cloud-ec-marketplace-azure005.png b/images/cloud-ec-marketplace-azure005.png new file mode 100644 index 0000000000..048e2e4691 Binary files /dev/null and b/images/cloud-ec-marketplace-azure005.png differ diff --git a/images/cloud-ec-marketplace-azure006.png b/images/cloud-ec-marketplace-azure006.png new file mode 100644 index 0000000000..320d9c7367 Binary files /dev/null and b/images/cloud-ec-marketplace-azure006.png differ diff --git a/images/cloud-ec-marketplace-azure009.png b/images/cloud-ec-marketplace-azure009.png new file mode 100644 index 0000000000..ea7befffbb Binary files /dev/null and b/images/cloud-ec-marketplace-azure009.png differ diff --git a/images/cloud-ec-migrate-deployment-template(2).png b/images/cloud-ec-migrate-deployment-template(2).png new file mode 100644 index 0000000000..518a93287f Binary files /dev/null and b/images/cloud-ec-migrate-deployment-template(2).png differ diff --git a/images/cloud-ec-new-hardware-profile-version.png b/images/cloud-ec-new-hardware-profile-version.png new file mode 100644 index 0000000000..bc9f4792c1 Binary files /dev/null and b/images/cloud-ec-new-hardware-profile-version.png differ diff --git a/images/cloud-ec-preview-different-profile-changes.png b/images/cloud-ec-preview-different-profile-changes.png new file mode 100644 index 0000000000..6eee388f1a Binary files /dev/null and b/images/cloud-ec-preview-different-profile-changes.png differ diff --git a/images/cloud-ec-preview-hardware-profile.png b/images/cloud-ec-preview-hardware-profile.png new file mode 100644 index 0000000000..ebc4fa9775 Binary files /dev/null and b/images/cloud-ec-preview-hardware-profile.png differ diff --git a/images/cloud-ec-preview-profile-changes.png b/images/cloud-ec-preview-profile-changes.png new file mode 100644 index 0000000000..5e3e242f0b Binary files /dev/null and b/images/cloud-ec-preview-profile-changes.png differ diff --git a/images/cloud-edit-trust-environment.png b/images/cloud-edit-trust-environment.png new file mode 100644 index 0000000000..7528bab224 Binary files /dev/null and b/images/cloud-edit-trust-environment.png differ diff --git a/images/cloud-enterprise-ce-copy-remote-cluster-parameters.png b/images/cloud-enterprise-ce-copy-remote-cluster-parameters.png new file mode 100644 index 0000000000..325cf37509 Binary files /dev/null and b/images/cloud-enterprise-ce-copy-remote-cluster-parameters.png differ diff --git a/images/cloud-enterprise-ce-create-from-snapshot-updated.png b/images/cloud-enterprise-ce-create-from-snapshot-updated.png new file mode 100644 index 0000000000..dbc7aacc01 Binary files /dev/null and b/images/cloud-enterprise-ce-create-from-snapshot-updated.png differ diff --git a/images/cloud-enterprise-delete-trust-environment.png b/images/cloud-enterprise-delete-trust-environment.png new file mode 100644 index 0000000000..a376e85672 Binary files /dev/null and b/images/cloud-enterprise-delete-trust-environment.png differ diff --git a/images/cloud-enterprise-ec-ce-autoscaling-data-summary2.png b/images/cloud-enterprise-ec-ce-autoscaling-data-summary2.png new file mode 100644 index 0000000000..f650fdfb28 Binary files /dev/null and b/images/cloud-enterprise-ec-ce-autoscaling-data-summary2.png differ diff --git a/images/cloud-enterprise-ec-ce-autoscaling-ml-summary2.png b/images/cloud-enterprise-ec-ce-autoscaling-ml-summary2.png new file mode 100644 index 0000000000..8380f8736d Binary files /dev/null and b/images/cloud-enterprise-ec-ce-autoscaling-ml-summary2.png differ diff --git a/images/cloud-enterprise-ec-customize-deployment2.png b/images/cloud-enterprise-ec-customize-deployment2.png new file mode 100644 index 0000000000..962409b57f Binary files /dev/null and b/images/cloud-enterprise-ec-customize-deployment2.png differ diff --git a/images/cloud-enterprise-ec-number-of-nodes.png b/images/cloud-enterprise-ec-number-of-nodes.png new file mode 100644 index 0000000000..65b8f1db00 Binary files /dev/null and b/images/cloud-enterprise-ec-number-of-nodes.png differ diff --git a/images/cloud-enterprise-ece-available-capacity.png b/images/cloud-enterprise-ece-available-capacity.png new file mode 100644 index 0000000000..fe22914e33 Binary files /dev/null and b/images/cloud-enterprise-ece-available-capacity.png differ diff --git a/images/cloud-enterprise-ece-aws-private-ip.png b/images/cloud-enterprise-ece-aws-private-ip.png new file mode 100644 index 0000000000..1623a83098 Binary files /dev/null and b/images/cloud-enterprise-ece-aws-private-ip.png differ diff --git a/images/cloud-enterprise-ece-aws-public-ip.png b/images/cloud-enterprise-ece-aws-public-ip.png new file mode 100644 index 0000000000..b3010ab2b4 Binary files /dev/null and b/images/cloud-enterprise-ece-aws-public-ip.png differ diff --git a/images/cloud-enterprise-ece-create-template-autoscaling.png b/images/cloud-enterprise-ece-create-template-autoscaling.png new file mode 100644 index 0000000000..c2dfa513cb Binary files /dev/null and b/images/cloud-enterprise-ece-create-template-autoscaling.png differ diff --git a/images/cloud-enterprise-ece-create-template-availability-zones.png b/images/cloud-enterprise-ece-create-template-availability-zones.png new file mode 100644 index 0000000000..b7a18b6c3b Binary files /dev/null and b/images/cloud-enterprise-ece-create-template-availability-zones.png differ diff --git a/images/cloud-enterprise-ece-create-template-initial-size.png b/images/cloud-enterprise-ece-create-template-initial-size.png new file mode 100644 index 0000000000..b45a673d9a Binary files /dev/null and b/images/cloud-enterprise-ece-create-template-initial-size.png differ diff --git a/images/cloud-enterprise-ece-create-template-instance-configuration.png b/images/cloud-enterprise-ece-create-template-instance-configuration.png new file mode 100644 index 0000000000..57bb530c45 Binary files /dev/null and b/images/cloud-enterprise-ece-create-template-instance-configuration.png differ diff --git a/images/cloud-enterprise-ece-create-template-max-autoscaling.png b/images/cloud-enterprise-ece-create-template-max-autoscaling.png new file mode 100644 index 0000000000..5902e557bb Binary files /dev/null and b/images/cloud-enterprise-ece-create-template-max-autoscaling.png differ diff --git a/images/cloud-enterprise-ece-create-template-user-settings.png b/images/cloud-enterprise-ece-create-template-user-settings.png new file mode 100644 index 0000000000..eeb621a395 Binary files /dev/null and b/images/cloud-enterprise-ece-create-template-user-settings.png differ diff --git a/images/cloud-enterprise-ece-query-ui.png b/images/cloud-enterprise-ece-query-ui.png new file mode 100644 index 0000000000..ddfa8d0d38 Binary files /dev/null and b/images/cloud-enterprise-ece-query-ui.png differ diff --git a/images/cloud-enterprise-ece-secure-settings.png b/images/cloud-enterprise-ece-secure-settings.png new file mode 100644 index 0000000000..b87f9cf69e Binary files /dev/null and b/images/cloud-enterprise-ece-secure-settings.png differ diff --git a/images/cloud-enterprise-ece-tagging-ui.png b/images/cloud-enterprise-ece-tagging-ui.png new file mode 100644 index 0000000000..8441726ffe Binary files /dev/null and b/images/cloud-enterprise-ece-tagging-ui.png differ diff --git a/images/cloud-enterprise-edit-trust-environment.png b/images/cloud-enterprise-edit-trust-environment.png new file mode 100644 index 0000000000..7528bab224 Binary files /dev/null and b/images/cloud-enterprise-edit-trust-environment.png differ diff --git a/images/cloud-enterprise-podman-migration-correct-role-1.png b/images/cloud-enterprise-podman-migration-correct-role-1.png new file mode 100644 index 0000000000..d1b413a076 Binary files /dev/null and b/images/cloud-enterprise-podman-migration-correct-role-1.png differ diff --git a/images/cloud-enterprise-podman-migration-fetch-roles-1.png b/images/cloud-enterprise-podman-migration-fetch-roles-1.png new file mode 100644 index 0000000000..4f3df81598 Binary files /dev/null and b/images/cloud-enterprise-podman-migration-fetch-roles-1.png differ diff --git a/images/cloud-enterprise-podman-migration-fetch-roles-2.png b/images/cloud-enterprise-podman-migration-fetch-roles-2.png new file mode 100644 index 0000000000..48daa7bd15 Binary files /dev/null and b/images/cloud-enterprise-podman-migration-fetch-roles-2.png differ diff --git a/images/cloud-enterprise-podman-migration-move-instances-1.png b/images/cloud-enterprise-podman-migration-move-instances-1.png new file mode 100644 index 0000000000..647d8f6986 Binary files /dev/null and b/images/cloud-enterprise-podman-migration-move-instances-1.png differ diff --git a/images/cloud-enterprise-podman-migration-wrong-role-1.png b/images/cloud-enterprise-podman-migration-wrong-role-1.png new file mode 100644 index 0000000000..b077760d1e Binary files /dev/null and b/images/cloud-enterprise-podman-migration-wrong-role-1.png differ diff --git a/images/cloud-heroku-ec-ce-autoscaling-data-summary2.png b/images/cloud-heroku-ec-ce-autoscaling-data-summary2.png new file mode 100644 index 0000000000..f650fdfb28 Binary files /dev/null and b/images/cloud-heroku-ec-ce-autoscaling-data-summary2.png differ diff --git a/images/cloud-heroku-ec-ce-autoscaling-ml-summary2.png b/images/cloud-heroku-ec-ce-autoscaling-ml-summary2.png new file mode 100644 index 0000000000..8380f8736d Binary files /dev/null and b/images/cloud-heroku-ec-ce-autoscaling-ml-summary2.png differ diff --git a/images/kibana-addFilterOptions_dashboard_8.6.0.png b/images/kibana-addFilterOptions_dashboard_8.6.0.png new file mode 100644 index 0000000000..fe81284499 Binary files /dev/null and b/images/kibana-addFilterOptions_dashboard_8.6.0.png differ diff --git a/images/kibana-addFilter_dashboard_8.6.0.png b/images/kibana-addFilter_dashboard_8.6.0.png new file mode 100644 index 0000000000..45bac56284 Binary files /dev/null and b/images/kibana-addFilter_dashboard_8.6.0.png differ diff --git a/images/kibana-add_content_to_dashboard_8.15.0.png b/images/kibana-add_content_to_dashboard_8.15.0.png new file mode 100644 index 0000000000..8a8b9b9d5d Binary files /dev/null and b/images/kibana-add_content_to_dashboard_8.15.0.png differ diff --git a/images/kibana-availableFields_discover_8.4.0.png b/images/kibana-availableFields_discover_8.4.0.png new file mode 100644 index 0000000000..ba3b9ecaeb Binary files /dev/null and b/images/kibana-availableFields_discover_8.4.0.png differ diff --git a/images/kibana-canvas_tutorialCustomImage_7.17.0.png b/images/kibana-canvas_tutorialCustomImage_7.17.0.png new file mode 100644 index 0000000000..5cca761ccc Binary files /dev/null and b/images/kibana-canvas_tutorialCustomImage_7.17.0.png differ diff --git a/images/kibana-dashboard-add-control-8.15.0.png b/images/kibana-dashboard-add-control-8.15.0.png new file mode 100644 index 0000000000..d4a21b32c4 Binary files /dev/null and b/images/kibana-dashboard-add-control-8.15.0.png differ diff --git a/images/kibana-dashboard-add-time-slider-control-8.15.0.png b/images/kibana-dashboard-add-time-slider-control-8.15.0.png new file mode 100644 index 0000000000..45c954e0c4 Binary files /dev/null and b/images/kibana-dashboard-add-time-slider-control-8.15.0.png differ diff --git a/images/kibana-dashboard-controls-settings-8.15.0.png b/images/kibana-dashboard-controls-settings-8.15.0.png new file mode 100644 index 0000000000..ea348115b2 Binary files /dev/null and b/images/kibana-dashboard-controls-settings-8.15.0.png differ diff --git a/images/kibana-dashboard_discoverDrilldown_8.3.png b/images/kibana-dashboard_discoverDrilldown_8.3.png new file mode 100644 index 0000000000..06ad04c8d1 Binary files /dev/null and b/images/kibana-dashboard_discoverDrilldown_8.3.png differ diff --git a/images/kibana-dashboard_drilldownOnPanel_8.3.png b/images/kibana-dashboard_drilldownOnPanel_8.3.png new file mode 100644 index 0000000000..e2df865c61 Binary files /dev/null and b/images/kibana-dashboard_drilldownOnPanel_8.3.png differ diff --git a/images/kibana-dashboard_ecommerceRevenueDashboard_8.6.0.png b/images/kibana-dashboard_ecommerceRevenueDashboard_8.6.0.png new file mode 100644 index 0000000000..ceaedbbd20 Binary files /dev/null and b/images/kibana-dashboard_ecommerceRevenueDashboard_8.6.0.png differ diff --git a/images/kibana-dashboard_sampleDataAddFilter_8.6.0.png b/images/kibana-dashboard_sampleDataAddFilter_8.6.0.png new file mode 100644 index 0000000000..2ae7b29099 Binary files /dev/null and b/images/kibana-dashboard_sampleDataAddFilter_8.6.0.png differ diff --git a/images/kibana-ecommerceTreemap_lens_8.4.0.png b/images/kibana-ecommerceTreemap_lens_8.4.0.png new file mode 100644 index 0000000000..d933ce93de Binary files /dev/null and b/images/kibana-ecommerceTreemap_lens_8.4.0.png differ diff --git a/images/kibana-lens_advancedTutorial_numberOfCustomers_8.5.0.png b/images/kibana-lens_advancedTutorial_numberOfCustomers_8.5.0.png new file mode 100644 index 0000000000..ec3085da63 Binary files /dev/null and b/images/kibana-lens_advancedTutorial_numberOfCustomers_8.5.0.png differ diff --git a/images/kibana-lens_areaChartCumulativeNumberOfSalesOnWeekend_7.16.png b/images/kibana-lens_areaChartCumulativeNumberOfSalesOnWeekend_7.16.png new file mode 100644 index 0000000000..82e0337ffe Binary files /dev/null and b/images/kibana-lens_areaChartCumulativeNumberOfSalesOnWeekend_7.16.png differ diff --git a/images/kibana-lens_areaPercentageNumberOfOrdersByCategory_8.3.png b/images/kibana-lens_areaPercentageNumberOfOrdersByCategory_8.3.png new file mode 100644 index 0000000000..01b20fe0a1 Binary files /dev/null and b/images/kibana-lens_areaPercentageNumberOfOrdersByCategory_8.3.png differ diff --git a/images/kibana-lens_barChartCustomTimeInterval_8.3.png b/images/kibana-lens_barChartCustomTimeInterval_8.3.png new file mode 100644 index 0000000000..2a4c2abee2 Binary files /dev/null and b/images/kibana-lens_barChartCustomTimeInterval_8.3.png differ diff --git a/images/kibana-lens_barChartDistributionOfNumberField_7.16.png b/images/kibana-lens_barChartDistributionOfNumberField_7.16.png new file mode 100644 index 0000000000..631477e7d6 Binary files /dev/null and b/images/kibana-lens_barChartDistributionOfNumberField_7.16.png differ diff --git a/images/kibana-lens_clickAndDragZoom_7.16.gif b/images/kibana-lens_clickAndDragZoom_7.16.gif new file mode 100644 index 0000000000..65fed435df Binary files /dev/null and b/images/kibana-lens_clickAndDragZoom_7.16.gif differ diff --git a/images/kibana-lens_lineChartMetricOverTime_8.4.0.png b/images/kibana-lens_lineChartMetricOverTime_8.4.0.png new file mode 100644 index 0000000000..9ed9b4730f Binary files /dev/null and b/images/kibana-lens_lineChartMetricOverTime_8.4.0.png differ diff --git a/images/kibana-lens_lineChartMultipleDataSeries_7.16.png b/images/kibana-lens_lineChartMultipleDataSeries_7.16.png new file mode 100644 index 0000000000..373fc76b5d Binary files /dev/null and b/images/kibana-lens_lineChartMultipleDataSeries_7.16.png differ diff --git a/images/kibana-lens_mixedXYChart_7.16.png b/images/kibana-lens_mixedXYChart_7.16.png new file mode 100644 index 0000000000..76fc96a44a Binary files /dev/null and b/images/kibana-lens_mixedXYChart_7.16.png differ diff --git a/images/kibana-lens_pieChartCompareSubsetOfDocs_7.16.png b/images/kibana-lens_pieChartCompareSubsetOfDocs_7.16.png new file mode 100644 index 0000000000..fdeca77da2 Binary files /dev/null and b/images/kibana-lens_pieChartCompareSubsetOfDocs_7.16.png differ diff --git a/images/kibana-lens_tableTopFieldValues_7.16.png b/images/kibana-lens_tableTopFieldValues_7.16.png new file mode 100644 index 0000000000..64417a9a63 Binary files /dev/null and b/images/kibana-lens_tableTopFieldValues_7.16.png differ diff --git a/images/kibana-lens_treemapMultiLevelChart_7.16.png b/images/kibana-lens_treemapMultiLevelChart_7.16.png new file mode 100644 index 0000000000..6d772a32e9 Binary files /dev/null and b/images/kibana-lens_treemapMultiLevelChart_7.16.png differ diff --git a/images/kibana-line-chart-bottom-axis-8.16.0.png b/images/kibana-line-chart-bottom-axis-8.16.0.png new file mode 100644 index 0000000000..dd8aaa680f Binary files /dev/null and b/images/kibana-line-chart-bottom-axis-8.16.0.png differ diff --git a/images/kibana-line-chart-left-axis-8.16.0.png b/images/kibana-line-chart-left-axis-8.16.0.png new file mode 100644 index 0000000000..76a797d171 Binary files /dev/null and b/images/kibana-line-chart-left-axis-8.16.0.png differ diff --git a/images/kibana-sampleDataFilter_dashboard_8.6.0.png b/images/kibana-sampleDataFilter_dashboard_8.6.0.png new file mode 100644 index 0000000000..018a5a2174 Binary files /dev/null and b/images/kibana-sampleDataFilter_dashboard_8.6.0.png differ diff --git a/images/kibana-table-with-request-keyword-and-client-ip-8.16.0.png b/images/kibana-table-with-request-keyword-and-client-ip-8.16.0.png new file mode 100644 index 0000000000..d34aa4068a Binary files /dev/null and b/images/kibana-table-with-request-keyword-and-client-ip-8.16.0.png differ diff --git a/images/kibana-timeFilter_discover_8.4.0.png b/images/kibana-timeFilter_discover_8.4.0.png new file mode 100644 index 0000000000..73f13ef2b1 Binary files /dev/null and b/images/kibana-timeFilter_discover_8.4.0.png differ diff --git a/images/kibana-tutorial-top-values-of-field-8.16.0.png b/images/kibana-tutorial-top-values-of-field-8.16.0.png new file mode 100644 index 0000000000..de7b40554d Binary files /dev/null and b/images/kibana-tutorial-top-values-of-field-8.16.0.png differ diff --git a/images/kibana-tutorial-unique-count-of-client-ip-8.16.0.png b/images/kibana-tutorial-unique-count-of-client-ip-8.16.0.png new file mode 100644 index 0000000000..84dbb8d647 Binary files /dev/null and b/images/kibana-tutorial-unique-count-of-client-ip-8.16.0.png differ diff --git a/images/kibana-visualization-type-dropdown-8.16.0.png b/images/kibana-visualization-type-dropdown-8.16.0.png new file mode 100644 index 0000000000..a906e33fe4 Binary files /dev/null and b/images/kibana-visualization-type-dropdown-8.16.0.png differ diff --git a/images/kibana-visualizationTypeDropdown_lens_8.4.0.png b/images/kibana-visualizationTypeDropdown_lens_8.4.0.png new file mode 100644 index 0000000000..731327997c Binary files /dev/null and b/images/kibana-visualizationTypeDropdown_lens_8.4.0.png differ diff --git a/manage-data/data-store/index-types/set-up-data-stream.md b/manage-data/data-store/index-types/set-up-data-stream.md index b8099ac7b1..bacb5936f1 100644 --- a/manage-data/data-store/index-types/set-up-data-stream.md +++ b/manage-data/data-store/index-types/set-up-data-stream.md @@ -15,7 +15,7 @@ To set up a data stream, follow these steps: You can also [convert an index alias to a data stream](#convert-index-alias-to-data-stream). -::::{important} +::::{important} If you use {{fleet}}, {{agent}}, or {{ls}}, skip this tutorial. They all set up data streams for you. For {{fleet}} and {{agent}}, check out this [data streams documentation](https://www.elastic.co/guide/en/fleet/current/data-streams.html). For {{ls}}, check out the [data streams settings](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html#plugins-outputs-elasticsearch-data_stream) for the `elasticsearch output` plugin. @@ -24,7 +24,7 @@ For {{fleet}} and {{agent}}, check out this [data streams documentation](https:/ -## Create an index lifecycle policy [create-index-lifecycle-policy] +## Create an index lifecycle policy [create-index-lifecycle-policy] While optional, we recommend using {{ilm-init}} to automate the management of your data stream’s backing indices. {{ilm-init}} requires an index lifecycle policy. @@ -83,7 +83,7 @@ PUT _ilm/policy/my-lifecycle-policy ``` -## Create component templates [create-component-templates] +## Create component templates [create-component-templates] A data stream requires a matching index template. In most cases, you compose this index template using one or more component templates. You typically use separate component templates for mappings and index settings. This lets you reuse the component templates in multiple index templates. @@ -92,7 +92,7 @@ When creating your component templates, include: * A [`date`](https://www.elastic.co/guide/en/elasticsearch/reference/current/date.html) or [`date_nanos`](https://www.elastic.co/guide/en/elasticsearch/reference/current/date_nanos.html) mapping for the `@timestamp` field. If you don’t specify a mapping, {{es}} maps `@timestamp` as a `date` field with default options. * Your lifecycle policy in the `index.lifecycle.name` index setting. -::::{tip} +::::{tip} Use the [Elastic Common Schema (ECS)](https://www.elastic.co/guide/en/ecs/{{ecs_version}}) when mapping your fields. ECS fields integrate with several {{stack}} features by default. If you’re unsure how to map your fields, use [runtime fields](../mapping/define-runtime-fields-in-search-request.md) to extract fields from [unstructured content](https://www.elastic.co/guide/en/elasticsearch/reference/current/keyword.html#mapping-unstructured-content) at search time. For example, you can index a log message to a `wildcard` field and later extract IP addresses and other data from this field during a search. @@ -143,7 +143,7 @@ PUT _component_template/my-settings ``` -## Create an index template [create-index-template] +## Create an index template [create-index-template] Use your component templates to create an index template. Specify: @@ -171,7 +171,7 @@ PUT _index_template/my-index-template ``` -## Create the data stream [create-data-stream] +## Create the data stream [create-data-stream] [Indexing requests](use-data-stream.md#add-documents-to-a-data-stream) add documents to a data stream. These requests must use an `op_type` of `create`. Documents must include a `@timestamp` field. @@ -180,7 +180,7 @@ To automatically create your data stream, submit an indexing request that target ```console PUT my-data-stream/_bulk { "create":{ } } -{ "@timestamp": "2099-05-06T16:21:15.000Z", "message": "192.0.2.42 - - [06/May/2099:16:21:15 +0000] \"GET /images/elasticsearch-reference-bg.jpg HTTP/1.0\" 200 24736" } +{ "@timestamp": "2099-05-06T16:21:15.000Z", "message": "192.0.2.42 - - [06/May/2099:16:21:15 +0000] \"GET /images/bg.jpg HTTP/1.0\" 200 24736" } { "create":{ } } { "@timestamp": "2099-05-06T16:25:42.000Z", "message": "192.0.2.255 - - [06/May/2099:16:25:42 +0000] \"GET /favicon.ico HTTP/1.0\" 200 3638" } @@ -198,14 +198,14 @@ PUT _data_stream/my-data-stream ``` -## Secure the data stream [secure-data-stream] +## Secure the data stream [secure-data-stream] Use [index privileges](../../../deploy-manage/users-roles/cluster-or-deployment-auth/elasticsearch-privileges.md#privileges-list-indices) to control access to a data stream. Granting privileges on a data stream grants the same privileges on its backing indices. For an example, see [Data stream privileges](../../../deploy-manage/users-roles/cluster-or-deployment-auth/granting-privileges-for-data-streams-aliases.md#data-stream-privileges). -## Convert an index alias to a data stream [convert-index-alias-to-data-stream] +## Convert an index alias to a data stream [convert-index-alias-to-data-stream] Prior to {{es}} 7.9, you’d typically use an [index alias with a write index](../../lifecycle/index-lifecycle-management/tutorial-automate-rollover.md#manage-time-series-data-without-data-streams) to manage time series data. Data streams replace this functionality, require less maintenance, and automatically integrate with [data tiers](../../lifecycle/data-tiers.md). @@ -216,7 +216,7 @@ POST _data_stream/_migrate/my-time-series-data ``` -## Get information about a data stream [get-info-about-data-stream] +## Get information about a data stream [get-info-about-data-stream] To get information about a data stream in {{kib}}, open the main menu and go to **Stack Management > Index Management**. In the **Data Streams** view, click the data stream’s name. @@ -227,7 +227,7 @@ GET _data_stream/my-data-stream ``` -## Delete a data stream [delete-data-stream] +## Delete a data stream [delete-data-stream] To delete a data stream and its backing indices in {{kib}}, open the main menu and go to **Stack Management > Index Management**. In the **Data Streams** view, click the trash icon. The icon only displays if you have the `delete_index` [security privilege](../../../deploy-manage/users-roles/cluster-or-deployment-auth/elasticsearch-privileges.md) for the data stream. diff --git a/manage-data/data-store/mapping/explore-data-with-runtime-fields.md b/manage-data/data-store/mapping/explore-data-with-runtime-fields.md index ee9dbefc37..adf7110666 100644 --- a/manage-data/data-store/mapping/explore-data-with-runtime-fields.md +++ b/manage-data/data-store/mapping/explore-data-with-runtime-fields.md @@ -40,7 +40,7 @@ The final document is not a valid Apache log format, but we can account for that ```console POST /my-index-000001/_bulk?refresh {"index":{}} -{"timestamp":"2020-04-30T14:30:17-05:00","message":"40.135.0.0 - - [30/Apr/2020:14:30:17 -0500] \"GET /images/elasticsearch-reference-hm_bg.jpg HTTP/1.0\" 200 24736"} +{"timestamp":"2020-04-30T14:30:17-05:00","message":"40.135.0.0 - - [30/Apr/2020:14:30:17 -0500] \"GET /images/hm_bg.jpg HTTP/1.0\" 200 24736"} {"index":{}} {"timestamp":"2020-04-30T14:30:53-05:00","message":"232.0.0.0 - - [30/Apr/2020:14:30:53 -0500] \"GET /images/hm_bg.jpg HTTP/1.0\" 200 24736"} {"index":{}} @@ -48,7 +48,7 @@ POST /my-index-000001/_bulk?refresh {"index":{}} {"timestamp":"2020-04-30T14:31:19-05:00","message":"247.37.0.0 - - [30/Apr/2020:14:31:19 -0500] \"GET /french/splash_inet.html HTTP/1.0\" 200 3781"} {"index":{}} -{"timestamp":"2020-04-30T14:31:22-05:00","message":"247.37.0.0 - - [30/Apr/2020:14:31:22 -0500] \"GET /images/elasticsearch-reference-hm_nbg.jpg HTTP/1.0\" 304 0"} +{"timestamp":"2020-04-30T14:31:22-05:00","message":"247.37.0.0 - - [30/Apr/2020:14:31:22 -0500] \"GET /images/hm_nbg.jpg HTTP/1.0\" 304 0"} {"index":{}} {"timestamp":"2020-04-30T14:31:27-05:00","message":"252.0.0.0 - - [30/Apr/2020:14:31:27 -0500] \"GET /images/hm_bg.jpg HTTP/1.0\" 200 24736"} {"index":{}} diff --git a/manage-data/data-store/mapping/retrieve-runtime-field.md b/manage-data/data-store/mapping/retrieve-runtime-field.md index 88a4a2c0e0..2bd383fbdd 100644 --- a/manage-data/data-store/mapping/retrieve-runtime-field.md +++ b/manage-data/data-store/mapping/retrieve-runtime-field.md @@ -43,7 +43,7 @@ POST /my-index-000001/_bulk?refresh { "index": {}} { "@timestamp": "2020-06-21T15:00:01-05:00", "message" : "211.11.9.0 - - [2020-06-21T15:00:01-05:00] \"GET /english/index.html HTTP/1.0\" 304 0"} { "index": {}} -{ "@timestamp": "2020-04-30T14:30:17-05:00", "message" : "40.135.0.0 - - [2020-04-30T14:30:17-05:00] \"GET /images/elasticsearch-reference-hm_bg.jpg HTTP/1.0\" 200 24736"} +{ "@timestamp": "2020-04-30T14:30:17-05:00", "message" : "40.135.0.0 - - [2020-04-30T14:30:17-05:00] \"GET /images/hm_bg.jpg HTTP/1.0\" 200 24736"} { "index": {}} { "@timestamp": "2020-04-30T14:30:53-05:00", "message" : "232.0.0.0 - - [2020-04-30T14:30:53-05:00] \"GET /images/hm_bg.jpg HTTP/1.0\" 200 24736"} { "index": {}} @@ -53,13 +53,13 @@ POST /my-index-000001/_bulk?refresh { "index": {}} { "@timestamp": "2020-04-30T14:31:27-05:00", "message" : "252.0.0.0 - - [2020-04-30T14:31:27-05:00] \"GET /images/hm_bg.jpg HTTP/1.0\" 200 24736"} { "index": {}} -{ "@timestamp": "2020-04-30T14:31:29-05:00", "message" : "247.37.0.0 - - [2020-04-30T14:31:29-05:00] \"GET /images/elasticsearch-reference-hm_brdl.gif HTTP/1.0\" 304 0"} +{ "@timestamp": "2020-04-30T14:31:29-05:00", "message" : "247.37.0.0 - - [2020-04-30T14:31:29-05:00] \"GET /images/hm_brdl.gif HTTP/1.0\" 304 0"} { "index": {}} -{ "@timestamp": "2020-04-30T14:31:29-05:00", "message" : "247.37.0.0 - - [2020-04-30T14:31:29-05:00] \"GET /images/elasticsearch-reference-hm_arw.gif HTTP/1.0\" 304 0"} +{ "@timestamp": "2020-04-30T14:31:29-05:00", "message" : "247.37.0.0 - - [2020-04-30T14:31:29-05:00] \"GET /images/hm_arw.gif HTTP/1.0\" 304 0"} { "index": {}} -{ "@timestamp": "2020-04-30T14:31:32-05:00", "message" : "247.37.0.0 - - [2020-04-30T14:31:32-05:00] \"GET /images/elasticsearch-reference-nav_bg_top.gif HTTP/1.0\" 200 929"} +{ "@timestamp": "2020-04-30T14:31:32-05:00", "message" : "247.37.0.0 - - [2020-04-30T14:31:32-05:00] \"GET /images/nav_bg_top.gif HTTP/1.0\" 200 929"} { "index": {}} -{ "@timestamp": "2020-04-30T14:31:43-05:00", "message" : "247.37.0.0 - - [2020-04-30T14:31:43-05:00] \"GET /french/images/elasticsearch-reference-nav_venue_off.gif HTTP/1.0\" 304 0"} +{ "@timestamp": "2020-04-30T14:31:43-05:00", "message" : "247.37.0.0 - - [2020-04-30T14:31:43-05:00] \"GET /french/images/nav_venue_off.gif HTTP/1.0\" 304 0"} ``` @@ -154,7 +154,7 @@ This time, the response includes only two hits. The value for `day_of_week` (`Su The [`fields`](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-fields.html) parameter on the `_search` API can also be used to retrieve fields from the related indices via runtime fields with a type of `lookup`. -::::{note} +::::{note} Fields that are retrieved by runtime fields of type `lookup` can be used to enrich the hits in a search response. It’s not possible to query or aggregate on these fields. :::: diff --git a/manage-data/lifecycle/data-stream/tutorial-create-data-stream-with-lifecycle.md b/manage-data/lifecycle/data-stream/tutorial-create-data-stream-with-lifecycle.md index 1c0ce38607..e35412d3a6 100644 --- a/manage-data/lifecycle/data-stream/tutorial-create-data-stream-with-lifecycle.md +++ b/manage-data/lifecycle/data-stream/tutorial-create-data-stream-with-lifecycle.md @@ -12,7 +12,7 @@ To create a data stream with a built-in lifecycle, follow these steps: 3. [Retrieve lifecycle information](#retrieve-lifecycle-information) -## Create an index template [create-index-template-with-lifecycle] +## Create an index template [create-index-template-with-lifecycle] A data stream requires a matching [index template](../../data-store/templates.md). You can configure the data stream lifecycle by setting the `lifecycle` field in the index template the same as you do for mappings and index settings. You can define an index template that sets a lifecycle as follows: @@ -40,7 +40,7 @@ PUT _index_template/my-index-template ``` -## Create a data stream [create-data-stream-with-lifecycle] +## Create a data stream [create-data-stream-with-lifecycle] You can create a data stream in two ways: @@ -55,14 +55,14 @@ You can create a data stream in two ways: ```console PUT my-data-stream/_bulk { "create":{ } } - { "@timestamp": "2099-05-06T16:21:15.000Z", "message": "192.0.2.42 - - [06/May/2099:16:21:15 +0000] \"GET /images/elasticsearch-reference-bg.jpg HTTP/1.0\" 200 24736" } + { "@timestamp": "2099-05-06T16:21:15.000Z", "message": "192.0.2.42 - - [06/May/2099:16:21:15 +0000] \"GET /images/bg.jpg HTTP/1.0\" 200 24736" } { "create":{ } } { "@timestamp": "2099-05-06T16:25:42.000Z", "message": "192.0.2.255 - - [06/May/2099:16:25:42 +0000] \"GET /favicon.ico HTTP/1.0\" 200 3638" } ``` -## Retrieve lifecycle information [retrieve-lifecycle-information] +## Retrieve lifecycle information [retrieve-lifecycle-information] You can use the [get data stream lifecycle API](https://www.elastic.co/guide/en/elasticsearch/reference/current/data-streams-get-lifecycle.html) to see the data stream lifecycle of your data stream and the [explain data stream lifecycle API](https://www.elastic.co/guide/en/elasticsearch/reference/current/data-streams-explain-lifecycle.html) to see the exact state of each backing index. diff --git a/manage-data/lifecycle/data-stream/tutorial-migrate-ilm-managed-data-stream-to-data-stream-lifecycle.md b/manage-data/lifecycle/data-stream/tutorial-migrate-ilm-managed-data-stream-to-data-stream-lifecycle.md index b69303f338..90d9f65146 100644 --- a/manage-data/lifecycle/data-stream/tutorial-migrate-ilm-managed-data-stream-to-data-stream-lifecycle.md +++ b/manage-data/lifecycle/data-stream/tutorial-migrate-ilm-managed-data-stream-to-data-stream-lifecycle.md @@ -67,7 +67,7 @@ We’ll now index a document targetting `dsl-data-stream` to create the data str POST dsl-data-stream/_doc? { "@timestamp": "2023-10-18T16:21:15.000Z", - "message": "192.0.2.42 - - [06/May/2099:16:21:15 +0000] \"GET /images/elasticsearch-reference-bg.jpg HTTP/1.0\" 200 24736" + "message": "192.0.2.42 - - [06/May/2099:16:21:15 +0000] \"GET /images/bg.jpg HTTP/1.0\" 200 24736" } ``` diff --git a/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md b/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md index 175d8dd6a0..618360bb20 100644 --- a/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md +++ b/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md @@ -340,7 +340,7 @@ To automatically create your data stream, submit an indexing request that target ```console PUT my-data-stream/_bulk { "create":{ } } -{ "@timestamp": "2099-05-06T16:21:15.000Z", "message": "192.0.2.42 - - [06/May/2099:16:21:15 +0000] \"GET /images/elasticsearch-reference-bg.jpg HTTP/1.0\" 200 24736" } +{ "@timestamp": "2099-05-06T16:21:15.000Z", "message": "192.0.2.42 - - [06/May/2099:16:21:15 +0000] \"GET /images/bg.jpg HTTP/1.0\" 200 24736" } { "create":{ } } { "@timestamp": "2099-05-06T16:25:42.000Z", "message": "192.0.2.255 - - [06/May/2099:16:25:42 +0000] \"GET /favicon.ico HTTP/1.0\" 200 3638" } diff --git a/raw-migrated-files/cloud/cloud/ec-scenario_why_is_my_node_unavailable.md b/raw-migrated-files/cloud/cloud/ec-scenario_why_is_my_node_unavailable.md index 4e80c77c19..15b0a77572 100644 --- a/raw-migrated-files/cloud/cloud/ec-scenario_why_is_my_node_unavailable.md +++ b/raw-migrated-files/cloud/cloud/ec-scenario_why_is_my_node_unavailable.md @@ -79,7 +79,7 @@ If your {{es}} cluster is unhealthy and reports a status of red, then increasing 1. Log in to the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body). 2. From the {{es}} Service panel, click the **Quick link** icon corresponding to the deployment that you want to manage. - :::{image} ../../../images/cloud-quick-link-to-deployment.png + :::{image} ../../../images/cloud-ec-quick-link-to-deployment.png :alt: Quick link to the deployment page ::: @@ -122,7 +122,7 @@ If your {{es}} cluster is unhealthy and reports a status of red, the scale up co 3. From your deployment menu, go to the **Edit** page and increase the **Size per zone** for the data tiers identified at step 2. - :::{image} ../../../images/cloud-increase-size-per-zone.png + :::{image} ../../../images/cloud-ec-increase-size-per-zone.png :alt: Increase size per zone ::: @@ -138,7 +138,7 @@ If your {{es}} cluster is unhealthy and reports a status of red, the scale up co 1. Log in to the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body). 2. From the {{es}} Service panel, click the **Quick link** icon corresponding to the deployment that you want to manage. - :::{image} ../../../images/cloud-quick-link-to-deployment.png + :::{image} ../../../images/cloud-ec-quick-link-to-deployment.png :alt: Quick link to the deployment page ::: @@ -204,7 +204,7 @@ By default, the allowed CPU usage threshold is set at 85%. 1. Log in to the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body). 2. From the {{es}} Service panel, click the **Quick link** icon corresponding to the deployment that you want to manage. - :::{image} ../../../images/cloud-quick-link-to-deployment.png + :::{image} ../../../images/cloud-ec-quick-link-to-deployment.png :alt: Quick link to the deployment page ::: diff --git a/raw-migrated-files/docs-content/serverless/security-deploy-elastic-endpoint-ven.md b/raw-migrated-files/docs-content/serverless/security-deploy-elastic-endpoint-ven.md index a455dcad06..1f8461ee31 100644 --- a/raw-migrated-files/docs-content/serverless/security-deploy-elastic-endpoint-ven.md +++ b/raw-migrated-files/docs-content/serverless/security-deploy-elastic-endpoint-ven.md @@ -82,7 +82,7 @@ The following instructions apply only to {{elastic-endpoint}} version 8.0.0 and 1. Open the **System Settings** application. 2. In the left pane, select **Privacy & Security**. - :::{image} ../../../images/serverless-getting-started-install-endpoint-ven-privacy_security_ven.png + :::{image} ../../../images/serverless--getting-started-install-endpoint-ven-privacy_security_ven.png :alt: getting started install endpoint ven privacy security ven :class: screenshot :::