[DOCS] Fix path to images in connector docs (#217920)

Author: lcawl

docs/reference/connectors-kibana/bedrock-action-type.md

@@ -14,7 +14,7 @@ The {{bedrock}} connector uses [axios](https://github.com/axios/axios) to send a
 
 You can create connectors in **{{stack-manage-app}} > {{connectors-ui}}**.  For example:
 
-:::{image} ../images/bedrock-connector.png
+:::{image} /reference/images/bedrock-connector.png
 :alt: {{bedrock}} connector
 :class: screenshot
 :::
@@ -44,7 +44,7 @@ Secret
 
 You can test connectors as you’re creating or editing the connector in {{kib}}. For example:
 
-:::{image} ../images/bedrock-params.png
+:::{image} /reference/images/bedrock-params.png
 :alt: {{bedrock}} params test
 :class: screenshot
 :::

docs/reference/connectors-kibana/cases-action-type.md

@@ -16,7 +16,7 @@ To use this connector you must have `All` {{kib}} privileges for the **Cases** f
 
 You cannot manage this connector in **{{stack-manage-app}} > {{connectors-ui}}** or by using APIs. You also cannot create a Cases [preconfigured connector](/reference/connectors-kibana/pre-configured-connectors.md). It is available only when you’re creating a rule in {{kib}}. For example:
 
-:::{image} ../images/cases-action.png
+:::{image} /reference/images/cases-action.png
 :alt: Add a cases action while creating a rule in {{kib}} {{rules-ui}}
 :class: screenshot
 :::

docs/reference/connectors-kibana/cases-webhook-action-type.md

@@ -14,28 +14,28 @@ The {{webhook-cm}} connector uses [axios](https://github.com/axios/axios) to sen
 
 You can create connectors in **{{stack-manage-app}} > {{connectors-ui}}** or as needed when you’re creating a rule. In the first step, you must provide a name for the connector and its authentication details. For example:
 
-:::{image} ../images/cases-webhook-connector.png
+:::{image} /reference/images/cases-webhook-connector.png
 :alt: Set authentication details in the {{webhook-cm}} connector
 :class: screenshot
 :::
 
 In the second step, you must provide the information necessary to create cases in the external system. For example:
 
-:::{image} ../images/cases-webhook-connector-create-case.png
+:::{image} /reference/images/cases-webhook-connector-create-case.png
 :alt: Add case creation details in the {{webhook-cm}} connector
 :class: screenshot
 :::
 
 In the third step, you must provide information related to retrieving case details from the external system. For example:
 
-:::{image} ../images/cases-webhook-connector-get-case.png
+:::{image} /reference/images/cases-webhook-connector-get-case.png
 :alt: Add case retrieval details in the {{webhook-cm}} connector
 :class: screenshot
 :::
 
 In the fourth step, you must provide information necessary to update cases in the external system. You can also optionally provide information to add comments to cases. For example:
 
-:::{image} ../images/cases-webhook-connector-comments.png
+:::{image} /reference/images/cases-webhook-connector-comments.png
 :alt: Add case update and comment details in the {{webhook-cm}} connector
 :class: screenshot
 :::
@@ -168,7 +168,7 @@ Update case URL
 
 You can test connectors as you’re creating or editing the connector in {{kib}}. For example:
 
-:::{image} ../images/cases-webhook-test.png
+:::{image} /reference/images/cases-webhook-test.png
 :alt: {{webhook-cm}} params test
 :class: screenshot
 :::

docs/reference/connectors-kibana/crowdstrike-action-type.md

@@ -21,7 +21,7 @@ To use this connector, you must have authority to run {{endpoint-sec}} connector
 
 You can create connectors in **{{stack-manage-app}} > {{connectors-ui}}**. For example:
 
-:::{image} ../images/crowdstrike-connector.png
+:::{image} /reference/images/crowdstrike-connector.png
 :alt: CrowdStrike connector
 :class: screenshot
 :::

docs/reference/connectors-kibana/d3security-action-type.md

@@ -16,7 +16,7 @@ To create this connector, you must first configure a webhook key in your D3 SOAR
 
 You can create connectors in **{{stack-manage-app}} > {{connectors-ui}}**.  For example:
 
-:::{image} ../images/d3security-connector.png
+:::{image} /reference/images/d3security-connector.png
 :alt: D3 Security connector
 :class: screenshot
 :::
@@ -40,7 +40,7 @@ Token
 
 You can test connectors as you’re creating or editing the connector in {{kib}}. For example:
 
-:::{image} ../images/d3security-params-test.png
+:::{image} /reference/images/d3security-params-test.png
 :alt: D3 Security params test
 :class: screenshot
 :::

docs/reference/connectors-kibana/email-action-type.md

@@ -21,7 +21,7 @@ The email connector uses the SMTP protocol to send mail messages. Email message
 
 You can create connectors in **{{stack-manage-app}} > {{connectors-ui}}** or as needed when you’re creating a rule. For example:
 
-:::{image} ../images/email-connector.png
+:::{image} /reference/images/email-connector.png
 :alt: Email connector
 :class: screenshot
 :::
@@ -72,7 +72,7 @@ Password
 
 You can test connectors as you’re creating or editing the connector in {{kib}}. For example:
 
-:::{image} ../images/email-params-test.png
+:::{image} /reference/images/email-params-test.png
 :alt: Email params test
 :class: screenshot
 :::
@@ -158,35 +158,35 @@ The email connector uses Microsoft Graph REST API v1.0, in particular the [sendM
 
 Before you create an email connector for Microsoft Exchange, you must create and register the client integration application on the [Azure portal](https://go.microsoft.com/fwlink/?linkid=2083908):
 
-:::{image} ../images/exchange-register-app.png
+:::{image} /reference/images/exchange-register-app.png
 :alt: Register client application for MS Exchange
 :class: screenshot
 :::
 
 Next, open **Manage > API permissions**, and then define the permissions for the registered application to send emails. Refer to the [documentation](https://docs.microsoft.com/en-us/graph/api/user-sendmail?view=graph-rest-1.0&tabs=http#permissions) for the Microsoft Graph API.
 
-:::{image} ../images/exchange-api-permissions.png
+:::{image} /reference/images/exchange-api-permissions.png
 :alt: MS Exchange API permissions
 :class: screenshot
 :::
 
 Add the "Mail.Send" permission for Microsoft Graph. The permission appears in the list with the status "Not granted for <your Azure active directory>":
 
-:::{image} ../images/exchange-not-granted.png
+:::{image} /reference/images/exchange-not-granted.png
 :alt: MS Exchange "Mail.Send" not granted
 :class: screenshot
 :::
 
 Click **Grant admin consent for <your Azure active directory>**.
 
-:::{image} ../images/exchange-grant-confirm.png
+:::{image} /reference/images/exchange-grant-confirm.png
 :alt: MS Exchange grant confirmation
 :class: screenshot
 :::
 
 Confirm that the status for the "Mail.Send" permission is now granted.
 
-:::{image} ../images/exchange-granted.png
+:::{image} /reference/images/exchange-granted.png
 :alt: MS Exchange grant confirmation
 :class: screenshot
 :::
@@ -196,7 +196,7 @@ Confirm that the status for the "Mail.Send" permission is now granted.
 
 To configure the Microsoft Exchange Client secret, open **Manage > Certificates & secrets**:
 
-:::{image} ../images/exchange-secrets.png
+:::{image} /reference/images/exchange-secrets.png
 :alt: MS Exchange secrets configuration
 :class: screenshot
 :::
@@ -208,7 +208,7 @@ Add a new client secret, then copy the value and put it to the proper field in t
 
 To find the Microsoft Exchange client and tenant IDs, open the **Overview** page:
 
-:::{image} ../images/exchange-client-tenant.png
+:::{image} /reference/images/exchange-client-tenant.png
 :alt: MS Exchange Client ID and Tenant ID configuration
 :class: screenshot
 :::

docs/reference/connectors-kibana/gemini-action-type.md

@@ -14,7 +14,7 @@ The {{gemini}} connector uses [axios](https://github.com/axios/axios) to send a
 
 You can create connectors in **{{stack-manage-app}} > {{connectors-ui}}**.  For example:
 
-:::{image} ../images/gemini-connector.png
+:::{image} /reference/images/gemini-connector.png
 :alt: {{gemini}} connector
 :class: screenshot
 :::
@@ -47,7 +47,7 @@ Credentials JSON
 
 You can test connectors as you’re creating or editing the connector in {{kib}}. For example:
 
-:::{image} ../images/gemini-params.png
+:::{image} /reference/images/gemini-params.png
 :alt: {{gemini}} params test
 :class: screenshot
 :::

docs/reference/connectors-kibana/index-action-type.md

@@ -14,7 +14,7 @@ An index connector indexes a document into {{es}}.
 
 You can create connectors in **{{stack-manage-app}} > {{connectors-ui}}** or as needed when you’re creating a rule. For example:
 
-:::{image} ../images/index-connector.png
+:::{image} /reference/images/index-connector.png
 :alt: Index connector
 :class: screenshot
 :::
@@ -29,7 +29,7 @@ Index connectors must have a name and an {{es}} index. You can optionally choose
 
 You can test connectors as you’re creating or editing the connector in {{kib}}. For example:
 
-:::{image} ../images/index-params-test.png
+:::{image} /reference/images/index-params-test.png
 :alt: Index params test
 :class: screenshot
 :::

docs/reference/connectors-kibana/jira-action-type.md

@@ -19,7 +19,7 @@ Jira Cloud and Jira Data Center are supported. Jira on-premise deployments are n
 
 You can create connectors in **{{stack-manage-app}} > {{connectors-ui}}** or as needed when you’re creating a rule. For example:
 
-:::{image} ../images/jira-connector.png
+:::{image} /reference/images/jira-connector.png
 :alt: Jira connector
 :class: screenshot
 :::
@@ -49,7 +49,7 @@ API token
 
 You can test connectors as you’re creating or editing the connector in {{kib}}. For example:
 
-:::{image} ../images/jira-params-test.png
+:::{image} /reference/images/jira-params-test.png
 :alt: Jira params test
 :class: screenshot
 :::

docs/reference/connectors-kibana/obs-ai-assistant-action-type.md

@@ -21,7 +21,7 @@ To learn how to interact with the assistant through this connector, refer to the
 
 To use this connector, you must have been granted access to use the Observability AI Assistant feature. You cannot manage this connector in **{{stack-manage-app}} > {{connectors-ui}}** or by using APIs. You also cannot create an Observability AI Assistant [preconfigured connector](/reference/connectors-kibana/pre-configured-connectors.md). It is available only when you’re creating a rule in {{kib}}. For example:
 
-:::{image} ../images/obs-ai-assistant-action.png
+:::{image} /reference/images/obs-ai-assistant-action.png
 :alt: Add an Observability AI Assistant action while creating a rule in the Observability UI
 :class: screenshot
 :::