Skip to content

Commit eddfb57

Browse files
authored
Move images to solutions folder (#1082)
1 parent c4fd693 commit eddfb57

16 files changed

+14
-14
lines changed

reference/apm/observability/apm.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ mapped_pages:
77

88
Elastic APM is an application performance monitoring system built on the {{stack}}. It allows you to monitor software services and applications in real time, by collecting detailed performance information on response time for incoming requests, database queries, calls to caches, external HTTP requests, and more. This makes it easy to pinpoint and fix performance problems quickly.
99

10-
:::{image} /reference/images/observability-apm-app-landing.png
10+
:::{image} /reference/apm/images/observability-apm-app-landing.png
1111
:alt: Applications UI in {kib}
1212
:screenshot:
1313
:::

solutions/observability/applications/llm-observability.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ Check [these instructions](https://elastic.github.io/opentelemetry/use-cases/llm
4444

4545
For an SRE team optimizing a customer support system powered by Azure OpenAI, Elastic’s [Azure OpenAI integration](https://www.elastic.co/guide/en/integrations/current/azure_openai.html) provides critical insights. They can quickly identify which model variants experience higher latency or error rates, enabling smarter decisions on model deployment or even switching providers based on real-time performance metrics.
4646

47-
:::{image} ../../../images/llm-performance-reliability.png
47+
:::{image} /solutions/images/llm-performance-reliability.png
4848
:alt: LLM performance and reliability
4949
:screenshot:
5050
:::
@@ -53,7 +53,7 @@ For an SRE team optimizing a customer support system powered by Azure OpenAI, El
5353

5454
Consider an enterprise utilizing an OpenAI model for real-time user interactions. Encountering unexplained delays, an SRE can use OpenAI tracing to dissect the transaction pathway, identify if one specific API call or model invocation is the bottleneck, and monitor a request to see the exact prompt and response between the user and the LLM.
5555

56-
:::{image} ../../../images/llm-openai-applications.png
56+
:::{image} /solutions/images/llm-openai-applications.png
5757
:alt: Troubleshoot OpenAI-powered applications
5858
:screenshot:
5959
:::
@@ -62,7 +62,7 @@ Consider an enterprise utilizing an OpenAI model for real-time user interactions
6262

6363
For cost-sensitive deployments, being acutely aware of which LLM configurations are more cost-effective is crucial. Elastic’s dashboards, pre-configured to display model usage patterns, help mitigate unnecessary spending effectively. You can use out-of-the-box dashboards for metrics, logs, and traces.
6464

65-
:::{image} ../../../images/llm-costs-usage-concerns.png
65+
:::{image} /solutions/images/llm-costs-usage-concerns.png
6666
:alt: LLM cost and usage concerns
6767
:screenshot:
6868
:::
@@ -71,7 +71,7 @@ For cost-sensitive deployments, being acutely aware of which LLM configurations
7171

7272
With the Elastic Amazon Bedrock integration for Guardrails, SREs can swiftly address security concerns, like verifying if certain user interactions prompt policy violations. Elastic's observability logs clarify whether guardrails rightly blocked potentially harmful responses, bolstering compliance assurance.
7373

74-
:::{image} ../../../images/llm-amazon-bedrock-guardrails.png
74+
:::{image} /solutions/images/llm-amazon-bedrock-guardrails.png
7575
:alt: Elastic Amazon Bedrock integration for Guardrails
7676
:screenshot:
7777
:::

solutions/security/ai/ai-assistant.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -87,14 +87,14 @@ Use these features to adjust and act on your conversations with AI Assistant:
8787
* (Optional) Select a *System Prompt* at the beginning of a conversation by using the **Select Prompt** menu. System Prompts provide context to the model, informing its response. To create a System Prompt, open the System Prompts dropdown menu and click **+ Add new System Prompt…​**.
8888
* (Optional) Select a *Quick Prompt* at the bottom of the chat window to get help writing a prompt for a specific purpose, such as summarizing an alert or converting a query from a legacy SIEM to {{elastic-sec}}.
8989

90-
:::{image} ../../images/security-quick-prompts.png
90+
:::{image} /solutions/images/security-quick-prompts.png
9191
:alt: Quick Prompts highlighted below a conversation
9292
:screenshot:
9393
:::
9494

9595
* System Prompts and Quick Prompts can also be configured from the corresponding tabs on the **Security AI settings** page.
9696

97-
:::{image} ../../images/security-assistant-settings-system-prompts.png
97+
:::{image} /solutions/images/security-assistant-settings-system-prompts.png
9898
:alt: The Security AI settings menu's System Prompts tab
9999
:::
100100

@@ -119,7 +119,7 @@ AI Assistant can remember particular information you tell it to remember. For ex
119119

120120
To adjust AI Assistant's settings from the chat window, click the **More** (three dots) button in the upper-right.
121121

122-
::::{image} ../../../images/security-attack-discovery-more-popover.png
122+
::::{image} /solutions/images/security-attack-discovery-more-popover.png
123123
:alt: AI Assistant's more options popover
124124
:screenshot:
125125
::::

solutions/security/ai/attack-discovery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ You need the `Attack Discovery: All` privilege to use Attack Discovery.
3939

4040
By default, Attack Discovery analyzes up to 100 alerts from the last 24 hours, but you can customize how many and which alerts it analyzes using the settings menu. To open it, click the gear icon next to the **Generate** button.
4141

42-
::::{image} ../../../images/security-attack-discovery-settings.png
42+
::::{image} /solutions/images/security-attack-discovery-settings.png
4343
:alt: Attack Discovery's settings menu
4444
:width: 500px
4545
::::

solutions/security/get-started/automatic-migration.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -19,19 +19,19 @@ You can ingest your data before migrating your rules, or migrate your rules firs
1919
* A working [LLM connector](/solutions/security/ai/set-up-connectors-for-large-language-models-llm.md).
2020
* {{stack}} users: an [Enterprise](https://www.elastic.co/pricing) subscription.
2121
* {{Stack}} users: {{ml}} must be enabled.
22-
* {{serverless-short}} users: a [Security Complete](../../../deploy-manage/deploy/elastic-cloud/project-settings.md) subscription.
22+
* {{serverless-short}} users: a [Security Complete](/deploy-manage/deploy/elastic-cloud/project-settings.md) subscription.
2323
* {{ecloud}} users: {{ml}} must be enabled. We recommend a minimum size of 4GB of RAM per {{ml}} zone.
2424

2525
::::
2626

2727
## Get started with Automatic Migration
2828

2929
1. Find **Get started** in the navigation menu or use the [global search bar](/explore-analyze/find-and-organize/find-apps-and-objects.md).
30-
2. Under **Configure AI provider**, select a configured model or [add a new one](/solutions/security/ai/set-up-connectors-for-large-language-models-llm.md). For information on how different models perform, refer to the [LLM performance matrix](../../../solutions/security/ai/large-language-model-performance-matrix.md).
30+
2. Under **Configure AI provider**, select a configured model or [add a new one](/solutions/security/ai/set-up-connectors-for-large-language-models-llm.md). For information on how different models perform, refer to the [LLM performance matrix](/solutions/security/ai/large-language-model-performance-matrix.md).
3131
3. Next, under **Migrate rules & add data**, click **Translate your existing SIEM rules to Elastic**, then **Upload rules**.
3232
4. Follow the instructions on the **Upload Splunk SIEM rules** flyout to export your rules from Splunk as JSON.
3333

34-
:::{image} ../../../images/security-siem-migration-1.png
34+
:::{image} /solutions/images/security-siem-migration-1.png
3535
:alt: the Upload Splunk SIEM rules flyout
3636
:width: 700px
3737
:screenshot:
@@ -70,7 +70,7 @@ This section describes the **Translated rules** page's interface and explains ho
7070

7171
When you upload a new batch of rules, they are assigned a name and number, for example `SIEM rule migration 1`, or `SIEM rule migration 2`. Use the **Migrations** dropdown menu in the upper right to select which batch appears.
7272

73-
::::{image} ../../../images/security-siem-migration-processed-rules.png
73+
::::{image} /solutions/images/security-siem-migration-processed-rules.png
7474
:alt: The translated rules page
7575
:width: 850px
7676
:screenshot:
@@ -115,7 +115,7 @@ You cannot edit Elastic-authored rules using this interface, but after they are
115115

116116
Click the rule's name to open the rule's details flyout to the **Translation** tab, which shows the source rule alongside the translated — or partially translated — Elastic version. You can update any part of the rule. When finished, click **Save**.
117117

118-
::::{image} ../../../images/security-siem-migration-edit-rule.png
118+
::::{image} /solutions/images/security-siem-migration-edit-rule.png
119119
:alt: The rule details flyout
120120
:width: 850px
121121
:screenshot:

0 commit comments

Comments
 (0)