[raw migrated files] Move images (#863)

Moves images per elastic/docs-builder#774 in
preparation for docs-assembler.

Author: colleenmcginnis

raw-migrated-files/cloud/cloud/ec-monitoring-setup.md

@@ -55,13 +55,13 @@ To learn more about what [Elasticsearch monitoring metrics](/deploy-manage/monit
 * The **Overview** tab includes information about the search and indexing performance of Elasticsearch and also provides log entries.
 * The **Nodes** tab can help you monitor cluster CPU performance, JVM strain, and free disk space.
 
-:::{image} ../../../images/cloud-ec-ce-monitoring-nodes.png
+:::{image} /raw-migrated-files/images/cloud-ec-ce-monitoring-nodes.png
 :alt: Node tab in Kibana under Stack Monitoring
 :::
 
 Some [performance metrics](/deploy-manage/monitor/access-performance-metrics-on-elastic-cloud.md) are also available directly in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) and don’t require looking at your monitoring deployment. If you’re ever in a rush to determine if there is a performance problem, you can get a quick overview by going to the **Performance** page from your deployment menu:
 
-:::{image} ../../../images/cloud-ec-ce-monitoring-performance.png
+:::{image} /raw-migrated-files/images/cloud-ec-ce-monitoring-performance.png
 :alt: Performance page of the Elastic Cloud console
 :::
 
@@ -78,26 +78,26 @@ If you suspect a performance issue, you can use your monitoring deployment to in
     1. Go to **Stack Management** > **Data Views** (formerly *Index Patterns*).
     2. Create a [data view](/explore-analyze/find-and-organize/data-views.md) for `elastic-cloud-logs*` and set **Timestamp field** to `@timestamp`:
 
-        :::{image} ../../../images/cloud-ec-ce-monitoring-logs.png
+        :::{image} /raw-migrated-files/images/cloud-ec-ce-monitoring-logs.png
         :alt: Create data view example in Kibana
         :::
 
 
 Navigate to the **Discover** or **Stream** pages to check if you’ve misconfigured your SAML authentication setup by filtering for `WARN` and `ERROR` level logs and viewing the specific `message` fields, for example:
 
-:::{image} ../../../images/cloud-ec-ce-monitoring-saml.png
+:::{image} /raw-migrated-files/images/cloud-ec-ce-monitoring-saml.png
 :alt: Log error in Stream page showing failed SAML authentication
 :::
 
 You can also use this page to test how problematic proxy traffic requests show up in audit logs. To illustrate, create a spurious test request from the [Elasticsearch API console](cloud://reference/cloud-hosted/ec-api-console.md):
 
-:::{image} ../../../images/cloud-ec-ce-monitoring-api-console.png
+:::{image} /raw-migrated-files/images/cloud-ec-ce-monitoring-api-console.png
 :alt: Elasticsearch API console showing a spurious request that fails
 :::
 
 You will get this request reported as a new log. Audit logs do not currently report the HTTP response status code, but they do report a correlating `event.action` column:
 
-:::{image} ../../../images/cloud-ec-ce-monitoring-new-log.png
+:::{image} /raw-migrated-files/images/cloud-ec-ce-monitoring-new-log.png
 :alt: New log entry that shows failed spurious request issued from the API console
 :::
 
@@ -122,7 +122,7 @@ On top of these default alerts that write to indices you can investigate, you mi
     3. Optional: Set up a customized message that helps you identify what the message is for.
     4. Select **Save**.
 
-    :::{image} ../../../images/cloud-ec-ce-monitoring-connector-action.png
+    :::{image} /raw-migrated-files/images/cloud-ec-ce-monitoring-connector-action.png
     :alt: Alert rule example showing settings to send a Slack notification based on CPU Usage
     :::
 
@@ -139,7 +139,7 @@ As a managed service, {{ecloud}} is here to help you manage the maintenance and
 
 When issues come up that you need to troubleshoot, you’ll frequently start with the same queries to determine which rabbit hole to investigate further, such as [`_cluster/health`](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-health) to determine overall deployment health.
 
-:::{image} ../../../images/cloud-ec-ce-monitoring-ongoing.png
+:::{image} /raw-migrated-files/images/cloud-ec-ce-monitoring-ongoing.png
 :alt: Elasticsearch API console showing queries useful for monitoring
 :::
 

raw-migrated-files/docs-content/serverless/observability-ai-assistant.md

@@ -5,7 +5,7 @@ The AI Assistant uses generative AI to provide:
 * **Chat**: Have conversations with the AI Assistant. Chat uses function calling to request, analyze, and visualize your data.
 * **Contextual insights**: Open prompts throughout {{obs-serverless}} that explain errors and messages and suggest remediation.
 
-:::{image} ../../../images/serverless-ai-assistant-overview.gif
+:::{image} /raw-migrated-files/images/serverless-ai-assistant-overview.gif
 :alt: Observability AI assistant preview
 :screenshot:
 :::
@@ -174,11 +174,11 @@ After every answer the LLM provides, let us know if the answer was helpful. Your
 
 ### Chat with the assistant [observability-ai-assistant-chat-with-the-assistant]
 
-Click the AI Assistant button (![AI Assistant icon](../../../images/serverless-ai-assistant-button.png "")) in the upper-right corner where available to start the chat.
+Click the AI Assistant button (![AI Assistant icon](/raw-migrated-files/images/serverless-ai-assistant-button.png "")) in the upper-right corner where available to start the chat.
 
 This opens the AI Assistant flyout, where you can ask the assistant questions about your instance:
 
-:::{image} ../../../images/serverless-ai-assistant-chat.png
+:::{image} /raw-migrated-files/images/serverless-ai-assistant-chat.png
 :alt: Observability AI assistant chat
 :screenshot:
 :::
@@ -233,14 +233,14 @@ AI Assistant contextual prompts throughout {{obs-serverless}} provide the follow
 
 For example, in the log details, you’ll see prompts for **What’s this message?** and **How do I find similar log messages?**:
 
-:::{image} ../../../images/serverless-ai-assistant-logs-prompts.png
+:::{image} /raw-migrated-files/images/serverless-ai-assistant-logs-prompts.png
 :alt: Observability AI assistant example prompts for logs
 :screenshot:
 :::
 
 Clicking a prompt generates a message specific to that log entry. You can continue a conversation from a contextual prompt by clicking **Start chat** to open the AI Assistant chat.
 
-:::{image} ../../../images/serverless-ai-assistant-logs.png
+:::{image} /raw-migrated-files/images/serverless-ai-assistant-logs.png
 :alt: Observability AI assistant example
 :screenshot:
 :::
@@ -255,7 +255,7 @@ You can use the [Observability AI Assistant connector](kibana://reference/connec
 3. In the **Connector** list, select the AI connector you created when you set up the assistant.
 4. In the **Message** field, specify the message to send to the assistant:
 
-:::{image} ../../../images/serverless-obs-ai-assistant-action-high-cpu.png
+:::{image} /raw-migrated-files/images/serverless-obs-ai-assistant-action-high-cpu.png
 :alt: Add an Observability AI assistant action while creating a rule in the Observability UI
 :screenshot:
 :::
@@ -272,7 +272,7 @@ Currently you can only send messages to Slack, email, Jira, PagerDuty, or a webh
 
 When the alert fires, contextual details about the event—such as when the alert fired, the service or host impacted, and the threshold breached—are sent to the AI Assistant, along with the message provided during configuration. The AI Assistant runs the tasks requested in the message and creates a conversation you can use to chat with the assistant:
 
-:::{image} ../../../images/serverless-obs-ai-assistant-output.png
+:::{image} /raw-migrated-files/images/serverless-obs-ai-assistant-output.png
 :alt: AI Assistant conversation created in response to an alert
 :screenshot:
 :::
@@ -289,7 +289,7 @@ Note that overly broad prompts may result in the request exceeding token limits.
 
 When asked to send a message to another connector, such as Slack, the AI Assistant attempts to include a link to the generated conversation.
 
-:::{image} ../../../images/serverless-obs-ai-assistant-slack-message.png
+:::{image} /raw-migrated-files/images/serverless-obs-ai-assistant-slack-message.png
 :alt: Message sent by Slack by the AI Assistant includes a link to the conversation
 :screenshot:
 :::

raw-migrated-files/docs-content/serverless/observability-ecs-application-logs.md

@@ -127,7 +127,7 @@ output.elasticsearch:
   api_key: "id:api_key"
 ```
 
-1. Set the `hosts` to your project’s {{es}} endpoint. Locate your project’s endpoint by clicking the help icon (![Help icon](../../../images/serverless-help.svg "")) and selecting **Endpoints**. Add the **{{es}} endpoint** to your configuration.
+1. Set the `hosts` to your project’s {{es}} endpoint. Locate your project’s endpoint by clicking the help icon (![Help icon](/raw-migrated-files/images/serverless-help.svg "")) and selecting **Endpoints**. Add the **{{es}} endpoint** to your configuration.
 2. From **Developer tools**, run the following command to create an API key that grants `manage` permissions for the `cluster` and the `filebeat-*` indices using:
 
     ```shell
@@ -348,7 +348,7 @@ To add the custom logs integration to your project:
 6. Add the **Log file path**. For example, `/var/log/your-logs.log`.
 7. Under **Custom log file**, click **Advanced options**.
 
-    ![Screenshot of advanced options location](../../../images/serverless-custom-logs-advanced-options.png "")
+    ![Screenshot of advanced options location](/raw-migrated-files/images/serverless-custom-logs-advanced-options.png "")
 
 8. In the **Processors** text box, add the following YAML configuration to add processors that enhance your data. See [processors](beats://reference/filebeat/filtering-enhancing-data.md) to learn more.
 

raw-migrated-files/docs-content/serverless/observability-plaintext-application-logs.md

@@ -95,7 +95,7 @@ output.elasticsearch:
   api_key: "id:api_key"
 ```
 
-1. Set the `hosts` to your project’s {{es}} endpoint. Locate your project’s endpoint by clicking the help icon (![Help icon](../../../images/serverless-help.svg "")) and selecting **Endpoints**. Add the **{{es}} endpoint** to your configuration.
+1. Set the `hosts` to your project’s {{es}} endpoint. Locate your project’s endpoint by clicking the help icon (![Help icon](/raw-migrated-files/images/serverless-help.svg "")) and selecting **Endpoints**. Add the **{{es}} endpoint** to your configuration.
 2. From **Developer tools**, run the following command to create an API key that grants `manage` permissions for the `cluster` and the `filebeat-*` indices using:
 
     ```shell

raw-migrated-files/docs-content/serverless/observability-stream-log-files.md

@@ -9,12 +9,12 @@ The **Admin** role or higher is required to onboard log data. To learn more, ref
 
 
 <div style="display:none">
-:::{image} ../../../images/serverless-logs-stream-logs-api-key-beats.png
+:::{image} /raw-migrated-files/images/serverless-logs-stream-logs-api-key-beats.png
 :alt: logs stream logs api key beats
 :screenshot:
 :::
 
-:::{image} ../../../images/serverless-log-copy-es-endpoint.png
+:::{image} /raw-migrated-files/images/serverless-log-copy-es-endpoint.png
 :alt: Copy a project's Elasticsearch endpoint
 :screenshot:
 :::
@@ -255,7 +255,7 @@ You need to set the values for the following fields:
     3. Click **View** next to *Endpoints*.
     4. Copy the *Elasticsearch endpoint*.
 
-    :::{image} ../../../images/serverless-log-copy-es-endpoint.png
+    :::{image} /raw-migrated-files/images/serverless-log-copy-es-endpoint.png
     :alt: Copy a project's Elasticsearch endpoint
     :screenshot:
     :::
@@ -295,7 +295,7 @@ You need to set the values for the following fields:
 
     3. You *must* set the API key to configure {{beats}}. Immediately after the API key is generated and while it is still being displayed, click the **Encoded** button next to the API key and select **Beats** from the list in the tooltip. Base64 encoded API keys are not currently supported in this configuration.
 
-        :::{image} ../../../images/serverless-logs-stream-logs-api-key-beats.png
+        :::{image} /raw-migrated-files/images/serverless-logs-stream-logs-api-key-beats.png
         :alt: logs stream logs api key beats
         :screenshot:
         :::

raw-migrated-files/images/cloud-ec-ce-monitoring-api-console.png

@@ -10,7 +10,7 @@ The AI Assistant uses generative AI to provide:
 * **Contextual insights** — open prompts throughout {{observability}} that explain errors and messages and suggest remediation.
 * **Chat** —  have conversations with the AI Assistant. Chat uses function calling to request, analyze, and visualize your data.
 
-:::{image} ../../../images/observability-obs-assistant2.gif
+:::{image} /raw-migrated-files/images/observability-obs-assistant2.gif
 :alt: Observability AI assistant preview
 :screenshot:
 :::
@@ -230,11 +230,11 @@ After every answer the LLM provides, let us know if the answer was helpful. Your
 
 ### Chat with the assistant [obs-ai-chat]
 
-Select the **AI Assistant** icon (![AI Assistant icon](../../../images/observability-ai-assistant-icon.png "")) at the upper-right corner of any {{observability}} application to start the chat.
+Select the **AI Assistant** icon (![AI Assistant icon](/raw-migrated-files/images/observability-ai-assistant-icon.png "")) at the upper-right corner of any {{observability}} application to start the chat.
 
 This opens the AI Assistant flyout, where you can ask the assistant questions about your instance:
 
-:::{image} ../../../images/observability-obs-ai-chat.png
+:::{image} /raw-migrated-files/images/observability-obs-ai-chat.png
 :alt: Observability AI assistant chat
 :screenshot:
 :::
@@ -307,14 +307,14 @@ AI Assistant contextual prompts throughout {{observability}} provide the followi
 
 For example, in the log details, you’ll see prompts for **What’s this message?** and **How do I find similar log messages?**:
 
-:::{image} ../../../images/observability-obs-ai-logs-prompts.png
+:::{image} /raw-migrated-files/images/observability-obs-ai-logs-prompts.png
 :alt: Observability AI assistant logs prompts
 :screenshot:
 :::
 
 Clicking a prompt generates a message specific to that log entry:
 
-:::{image} ../../../images/observability-obs-ai-logs.gif
+:::{image} /raw-migrated-files/images/observability-obs-ai-logs.gif
 :alt: Observability AI assistant example
 :screenshot:
 :::
@@ -331,7 +331,7 @@ Use the [Observability AI Assistant connector](kibana://reference/connectors-kib
 3. In the **Connector** list, select the AI connector you created when you set up the assistant.
 4. In the **Message** field, specify the message to send to the assistant:
 
-    :::{image} ../../../images/observability-obs-ai-assistant-action-high-cpu.png
+    :::{image} /raw-migrated-files/images/observability-obs-ai-assistant-action-high-cpu.png
     :alt: Add an Observability AI assistant action while creating a rule in the Observability UI
     :screenshot:
     :::
@@ -346,7 +346,7 @@ Currently only Slack, email, Jira, PagerDuty, or webhook actions are supported.
 
 When the alert fires, contextual details about the event—such as when the alert fired, the service or host impacted, and the threshold breached—are sent to the AI Assistant, along with the message provided during configuration. The AI Assistant runs the tasks requested in the message and creates a conversation you can use to chat with the assistant:
 
-:::{image} ../../../images/observability-obs-ai-assistant-output.png
+:::{image} /raw-migrated-files/images/observability-obs-ai-assistant-output.png
 :alt: AI Assistant conversation created in response to an alert
 :screenshot:
 :::
@@ -367,7 +367,7 @@ The `server.publicBaseUrl` setting must be correctly specified under {{kib}} set
 ::::
 
 
-:::{image} ../../../images/observability-obs-ai-assistant-slack-message.png
+:::{image} /raw-migrated-files/images/observability-obs-ai-assistant-slack-message.png
 :alt: Message sent by Slack by the AI Assistant includes a link to the conversation
 :screenshot:
 :::

raw-migrated-files/images/cloud-ec-ce-monitoring-connector-action.png

@@ -40,7 +40,7 @@ For the basic ports and protocols required for the installation to work, refer t
 
 Before starting, take a moment to familiarize yourself with the {{stack}} components.
 
-:::{image} ../../../images/elastic-stack-stack-install-final-state.png
+:::{image} /raw-migrated-files/images/elastic-stack-stack-install-final-state.png
 :alt: Image showing the relationships between stack components
 :::
 
@@ -619,7 +619,7 @@ View your system metrics data:
 2. In the query field, search for `Metrics System`.
 3. Select the `[Metrics System] Host overview` link. The {{kib}} Dashboard opens with visualizations of host metrics including CPU usage, memory usage, running processes, and others.
 
-    :::{image} ../../../images/elastic-stack-install-stack-metrics-dashboard.png
+    :::{image} /raw-migrated-files/images/elastic-stack-install-stack-metrics-dashboard.png
     :alt: The System metrics host overview showing CPU usage, memory usage, and other visualizations
     :::