[manage data] Move images

manage-data/data-store/data-streams.md

@@ -32,7 +32,7 @@ Keep in mind that some features such as [Time Series Data Streams (TSDS)](../dat
 
 A data stream consists of one or more [hidden](elasticsearch://reference/elasticsearch/index-settings/index-modules.md#index-hidden), auto-generated backing indices.
 
-:::{image} ../../images/elasticsearch-reference-data-streams-diagram.svg
+:::{image} /manage-data/images/elasticsearch-reference-data-streams-diagram.svg
 :alt: data streams diagram
 :::
 
@@ -49,7 +49,7 @@ The name pattern for the backing indices is an implementation detail and no inte
 
 When you submit a read request to a data stream, the stream routes the request to all its backing indices.
 
-:::{image} ../../images/elasticsearch-reference-data-streams-search-request.svg
+:::{image} /manage-data/images/elasticsearch-reference-data-streams-search-request.svg
 :alt: data streams search request
 :::
 
@@ -58,7 +58,7 @@ When you submit a read request to a data stream, the stream routes the request t
 
 The most recently created backing index is the data stream’s write index. The stream adds new documents to this index only.
 
-:::{image} ../../images/elasticsearch-reference-data-streams-index-request.svg
+:::{image} /manage-data/images/elasticsearch-reference-data-streams-index-request.svg
 :alt: data streams index request
 :::
 

manage-data/data-store/data-streams/downsampling-time-series-data-stream.md

@@ -27,26 +27,26 @@ Check the following sections to learn more:
 
 A [time series](time-series-data-stream-tsds.md#time-series) is a sequence of observations taken over time for a specific entity. The observed samples can be represented as a continuous function, where the time series dimensions remain constant and the time series metrics change over time.
 
-:::{image} ../../../images/elasticsearch-reference-time-series-function.png
+:::{image} /manage-data/images/elasticsearch-reference-time-series-function.png
 :alt: time series function
 :::
 
 In an Elasticsearch index, a single document is created for each timestamp, containing the immutable time series dimensions, together with the metrics names and the changing metrics values. For a single timestamp, several time series dimensions and metrics may be stored.
 
-:::{image} ../../../images/elasticsearch-reference-time-series-metric-anatomy.png
+:::{image} /manage-data/images/elasticsearch-reference-time-series-metric-anatomy.png
 :alt: time series metric anatomy
 :::
 
 For your most current and relevant data, the metrics series typically has a low sampling time interval, so it’s optimized for queries that require a high data resolution.
 
-:::{image} ../../../images/elasticsearch-reference-time-series-original.png
+:::{image} /manage-data/images/elasticsearch-reference-time-series-original.png
 :alt: time series original
 :title: Original metrics series
 :::
 
 Downsampling works on older, less frequently accessed data by replacing the original time series with both a data stream of a higher sampling interval and statistical representations of that data. Where the original metrics samples may have been taken, for example, every ten seconds, as the data ages you may choose to reduce the sample granularity to hourly or daily. You may choose to reduce the granularity of `cold` archival data to monthly or less.
 
-:::{image} ../../../images/elasticsearch-reference-time-series-downsampled.png
+:::{image} /manage-data/images/elasticsearch-reference-time-series-downsampled.png
 :alt: time series downsampled
 :title: Downsampled metrics series
 :::

manage-data/data-store/data-streams/manage-data-stream.md

@@ -14,7 +14,7 @@ A value in the data retention column indicates that the data stream is managed b
 
 In {{es-serverless}}, indices matching the `logs-*-*` pattern use the logsDB index mode by default. The logsDB index mode creates a [logs data stream](./logs-data-stream.md).
 
-:::{image} ../../../images/serverless-management-data-stream.png
+:::{image} /manage-data/images/serverless-management-data-stream.png
 :alt: Data stream details
 :screenshot:
 :::

manage-data/data-store/data-streams/time-series-data-stream-tsds.md

@@ -50,7 +50,7 @@ A time series is a sequence of observations for a specific entity. Together, the
 * The price of a stock
 * Temperature and humidity readings from a weather sensor.
 
-:::{image} ../../../images/elasticsearch-reference-time-series-chart.svg
+:::{image} /manage-data/images/elasticsearch-reference-time-series-chart.svg
 :alt: time series chart
 :title: Time series of weather sensor readings plotted as a graph
 :::
@@ -146,7 +146,7 @@ In a TSDS, each backing index, including the most recent backing index, has a ra
 
 When you add a document to a TSDS, {{es}} adds the document to the appropriate backing index based on its `@timestamp` value. As a result, a TSDS can add documents to any TSDS backing index that can receive writes. This applies even if the index isn’t the most recent backing index.
 
-:::{image} ../../../images/elasticsearch-reference-time-bound-indices.svg
+:::{image} /manage-data/images/elasticsearch-reference-time-bound-indices.svg
 :alt: time bound indices
 :::
 

manage-data/data-store/index-basics.md

@@ -73,7 +73,7 @@ Go to **{{project-settings}} → {{manage-app}} → {{index-manage-app}}**.
 
 Investigate your indices and perform operations from the **Indices** view.
 
-:::{image} /images/serverless-index-management-indices.png
+:::{image} /manage-data/images/serverless-index-management-indices.png
 :alt: Index Management indices
 :screenshot:
 :::
@@ -89,7 +89,7 @@ A [data stream](/manage-data/data-store/data-streams.md) lets you store append-o
 
 Investigate your data streams and address lifecycle management needs in the **Data Streams** view.
 
-:::{image} /images/serverless-management-data-stream.png
+:::{image} /manage-data/images/serverless-management-data-stream.png
 :alt: Data stream details
 :screenshot:
 :::
@@ -107,7 +107,7 @@ An [index template](/manage-data/data-store/templates.md) is a way to tell {{es}
 
 Create, edit, clone, and delete your index templates in the **Index Templates** view. Changes made to an index template do not affect existing indices.
 
-:::{image} /images/serverless-index-management-index-templates.png
+:::{image} /manage-data/images/serverless-index-management-index-templates.png
 :alt: Index templates
 :screenshot:
 :::
@@ -123,7 +123,7 @@ Create, edit, clone, and delete your index templates in the **Index Templates**
 
 Create, edit, clone, and delete your component templates in the **Component Templates** view.
 
-:::{image} /images/serverless-management-component-templates.png
+:::{image} /manage-data/images/serverless-management-component-templates.png
 :alt: Component templates
 :screenshot:
 :::
@@ -137,7 +137,7 @@ An [enrich policy](/manage-data/ingest/transform-enrich/data-enrichment.md#enric
 
 Add data from your existing indices to incoming documents using the **Enrich Policies** view.
 
-:::{image} /images/serverless-management-enrich-policies.png
+:::{image} /manage-data/images/serverless-management-enrich-policies.png
 :alt: Enrich policies
 :screenshot:
 :::

manage-data/data-store/near-real-time-search.md

@@ -13,15 +13,15 @@ Lucene, the Java libraries on which {{es}} is based, introduced the concept of p
 
 Sitting between {{es}} and the disk is the filesystem cache. Documents in the in-memory indexing buffer ([Figure 1](#img-pre-refresh)) are written to a new segment ([Figure 2](#img-post-refresh)). The new segment is written to the filesystem cache first (which is cheap) and only later is it flushed to disk (which is expensive). However, after a file is in the cache, it can be opened and read just like any other file.
 
-:::{image} /images/elasticsearch-reference-lucene-in-memory-buffer.png
+:::{image} /manage-data/images/elasticsearch-reference-lucene-in-memory-buffer.png
 :alt: A Lucene index with new documents in the in-memory buffer
 :title: A Lucene index with new documents in the in-memory buffer
 :name: img-pre-refresh
 :::
 
 Lucene allows new segments to be written and opened, making the documents they contain visible to search ​without performing a full commit. This is a much lighter process than a commit to disk, and can be done frequently without degrading performance.
 
-:::{image} /images/elasticsearch-reference-lucene-written-not-committed.png
+:::{image} /manage-data/images/elasticsearch-reference-lucene-written-not-committed.png
 :alt: The buffer contents are written to a segment, which is searchable, but is not yet committed
 :title: The buffer contents are written to a segment, which is searchable, but is not yet committed
 :name: img-post-refresh

manage-data/data-store/templates/index-template-management.md

@@ -11,7 +11,7 @@ applies_to:
 
 Create, edit, clone, and delete your index templates in the **Index Templates** view. Changes made to an index template do not affect existing indices.
 
-:::{image} ../../../images/elasticsearch-reference-management-index-templates.png
+:::{image} /manage-data/images/elasticsearch-reference-management-index-templates.png
 :alt: Index templates
 :screenshot:
 :::
@@ -28,7 +28,7 @@ In this tutorial, you’ll create an index template and use it to configure two
 
 1. In the **Index Templates** view, open the **Create template** wizard.
 
-    :::{image} ../../../images/elasticsearch-reference-management_index_create_wizard.png
+    :::{image} /manage-data/images/elasticsearch-reference-management_index_create_wizard.png
     :alt: Create wizard
     :screenshot:
     :::
@@ -45,15 +45,15 @@ In this tutorial, you’ll create an index template and use it to configure two
 
     Component templates are optional. For this tutorial, do not add any component templates.
 
-    :::{image} ../../../images/elasticsearch-reference-management_index_component_template.png
+    :::{image} /manage-data/images/elasticsearch-reference-management_index_component_template.png
     :alt: Component templates page
     :screenshot:
     :::
 
 2. Define index settings. These are optional. For this tutorial, leave this section blank.
 3. Define a mapping that contains an [object](elasticsearch://reference/elasticsearch/mapping-reference/object.md) field named `geo` with a child [`geo_point`](elasticsearch://reference/elasticsearch/mapping-reference/geo-point.md) field named `coordinates`:
 
-    :::{image} ../../../images/elasticsearch-reference-management-index-templates-mappings.png
+    :::{image} /manage-data/images/elasticsearch-reference-management-index-templates-mappings.png
     :alt: Mapped fields page
     :screenshot:
     :::

manage-data/data-store/text-analysis/token-graphs.md

@@ -15,7 +15,7 @@ When a [tokenizer](anatomy-of-an-analyzer.md#analyzer-anatomy-tokenizer) convert
 
 Using these, you can create a [directed acyclic graph](https://en.wikipedia.org/wiki/Directed_acyclic_graph), called a *token graph*, for a stream. In a token graph, each position represents a node. Each token represents an edge or arc, pointing to the next position.
 
-:::{image} ../../../images/elasticsearch-reference-token-graph-qbf-ex.svg
+:::{image} /manage-data/images/elasticsearch-reference-token-graph-qbf-ex.svg
 :alt: token graph qbf ex
 :::
 
@@ -25,7 +25,7 @@ Some [token filters](anatomy-of-an-analyzer.md#analyzer-anatomy-token-filters) c
 
 In the following graph, `quick` and its synonym `fast` both have a position of `0`. They span the same positions.
 
-:::{image} ../../../images/elasticsearch-reference-token-graph-qbf-synonym-ex.svg
+:::{image} /manage-data/images/elasticsearch-reference-token-graph-qbf-synonym-ex.svg
 :alt: token graph qbf synonym ex
 :::
 
@@ -43,7 +43,7 @@ Some tokenizers, such as the [`nori_tokenizer`](elasticsearch://reference/elasti
 
 In the following graph, `domain name system` and its synonym, `dns`, both have a position of `0`. However, `dns` has a `positionLength` of `3`. Other tokens in the graph have a default `positionLength` of `1`.
 
-:::{image} ../../../images/elasticsearch-reference-token-graph-dns-synonym-ex.svg
+:::{image} /manage-data/images/elasticsearch-reference-token-graph-dns-synonym-ex.svg
 :alt: token graph dns synonym ex
 :::
 
@@ -60,7 +60,7 @@ A user runs a search for the following phrase using the `match_phrase` query:
 
 During [search analysis](index-search-analysis.md), `dns`, a synonym for `domain name system`, is added to the query string’s token stream. The `dns` token has a `positionLength` of `3`.
 
-:::{image} ../../../images/elasticsearch-reference-token-graph-dns-synonym-ex.svg
+:::{image} /manage-data/images/elasticsearch-reference-token-graph-dns-synonym-ex.svg
 :alt: token graph dns synonym ex
 :::
 
@@ -88,7 +88,7 @@ This means these filters will produce invalid token graphs for streams containin
 
 In the following graph, `dns` is a multi-position synonym for `domain name system`. However, `dns` has the default `positionLength` value of `1`, resulting in an invalid graph.
 
-:::{image} ../../../images/elasticsearch-reference-token-graph-dns-invalid-ex.svg
+:::{image} /manage-data/images/elasticsearch-reference-token-graph-dns-invalid-ex.svg
 :alt: token graph dns invalid ex
 :::