From 18b6cd4e87bfbcb78c3e636ecc7095410068bb35 Mon Sep 17 00:00:00 2001 From: Andy Stark Date: Fri, 2 Oct 2026 11:29:23 +0100 Subject: [PATCH] DOC-7128 iris-radar-ri: convert iris/, radar/, and redisinsight/ images Runs build/migrate_image_shortcodes.py over 15 files in content/operate/iris/, radar/, and redisinsight/, converting all 86 image shortcodes to Markdown images (84 bare paths rewritten to site-root /images/...). None needed skipping, and these trees have no raw tags. Ticket: DOC-7128 Co-Authored-By: Claude Opus 5.5 --- .../iris/agent-memory/create-service.md | 27 ++++++++------ .../iris/agent-memory/model-configuration.md | 6 ++-- .../operate/iris/agent-memory/view-service.md | 28 ++++++++------- .../iris/context-retriever/create-service.md | 13 +++---- .../iris/context-retriever/view-admin-keys.md | 14 +++++--- .../iris/context-retriever/view-service.md | 10 +++--- .../operate/iris/langcache/create-service.md | 36 +++++++++++-------- .../operate/iris/langcache/monitor-cache.md | 2 +- .../operate/iris/langcache/view-edit-cache.md | 15 ++++---- content/operate/radar/agent.md | 12 ++++--- content/operate/radar/connect.md | 18 ++++++---- .../radar/licenses-and-certificates.md | 6 ++-- content/operate/radar/manage-access.md | 6 ++-- content/operate/radar/monitor.md | 18 ++++++---- content/operate/redisinsight/proxy.md | 4 +-- 15 files changed, 129 insertions(+), 86 deletions(-) diff --git a/content/operate/iris/agent-memory/create-service.md b/content/operate/iris/agent-memory/create-service.md index 331f9f6c50..c491fbdc9a 100644 --- a/content/operate/iris/agent-memory/create-service.md +++ b/content/operate/iris/agent-memory/create-service.md @@ -35,17 +35,20 @@ From the [Redis Cloud console](https://cloud.redis.io/), select **Agent Memory** If you have not already created an Agent Memory service, you'll see a page with an introduction to Agent Memory. Otherwise, select **New service** to go to the Agent Memory introduction page. -{{The New service button.}} +![The New service button.](/images/rc/langcache-new-service.png) +{width="150px"} From here: - Select **Quick create** to create a Redis Agent Memory service with default settings using your Free 30MB database. If you haven't created a Free database yet, Redis Cloud will create one and set up the Redis Agent Memory service for you. - {{The Quick create button.}} + ![The Quick create button.](/images/rc/langcache-quick-create.png) + {width="150px"} After Redis Cloud creates your Agent Memory service, a window containing your Agent Memory service key will appear. Select **Copy** to copy the key to your clipboard. - {{The Agent Memory service key window. Use the Copy button to save the service key to the clipboard.}} + ![The Agent Memory service key window. Use the Copy button to save the service key to the clipboard.](/images/rc/agent-memory-service-key.png) + {width="40%"} {{}} This is the only time the value of the user key is available. Save it to a secure location before closing the dialog box.

@@ -57,7 +60,8 @@ If you lose the service key value, you will need to [generate a new service key] - If you want to customize your Redis Agent Memory service, select **Create custom**. - {{The Create custom button to create an Agent Memory service.}} + ![The Create custom button to create an Agent Memory service.](/images/rc/agent-memory-custom-service.png) + {width="150px"} This takes you to the **Create Agent Memory Service** page. This page is divided into the following sections: @@ -71,7 +75,7 @@ If you lose the service key value, you will need to [generate a new service key] The **General settings** section defines basic properties of your service. -{{The General settings section.}} +![The General settings section.](/images/rc/agent-memory-general-settings.png) | Setting name |Description| |:----------------------|:----------| @@ -83,7 +87,7 @@ The **General settings** section defines basic properties of your service. The **Memory configuration** section allows you to define the time-to-live (TTL) of your agent's memories, set how often memories are extracted, and control automatic summarization of session memory. -{{The Memory configuration section.}} +![The Memory configuration section.](/images/rc/agent-memory-memory-configuration.png) | Setting name |Description| |:----------------------|:----------| @@ -112,7 +116,7 @@ Select **Use Redis in-built keys** to use Redis-managed model credentials. This LLM model options can change. Use the console to see the current choices; values shown in the screenshot are examples. -{{The AI model and credentials section with Bring my own key selected. The section contains the provider, API key, LLM model, and embedding model settings.}} +![The AI model and credentials section with Bring my own key selected. The section contains the provider, API key, LLM model, and embedding model settings.](/images/rc/agent-memory-ai-model-create.png) The same provider key is used for both model types. The credential source, provider, and embedding model are fixed after you create the service. For configuration, key rotation, security, and troubleshooting guidance, see [Configure AI models for Agent Memory]({{< relref "/operate/iris/agent-memory/model-configuration" >}}). @@ -120,7 +124,7 @@ The same provider key is used for both model types. The credential source, provi The **Memory types & extraction** section allows you to define custom long-term memory types with structured fields and an optional extraction strategy. Each enabled type runs independently. -{{The Memory types & extraction section.}} +![The Memory types & extraction section.](/images/rc/agent-memory-memory-types.png) #### Custom memory types @@ -169,7 +173,7 @@ Detector matches are applied deterministically. Semantic exclusions only steer t Sensitive-data exclusions are an early-stage feature, enabled for selected accounts. If you want to try them, contact your Redis representative or [contact sales](https://redis.io/contact/). {{< /note >}} -{{The Sensitive-data exclusions section.}} +![The Sensitive-data exclusions section.](/images/rc/agent-memory-sensitive-data-exclusions.png) Exclusions are applied when long-term memories are created from a session. Session memory is unaffected: events and their summaries are kept as sent. Exclusions are also not applied to long-term memories your application creates directly through the API or an SDK. @@ -232,11 +236,12 @@ Semantic exclusions are **advisory**. They steer the extraction model, but they When you are done setting the details of your Agent Memory service, select **Create** to create it. -{{Use the Create button to create an Agent Memory service.}} +![Use the Create button to create an Agent Memory service.](/images/rc/button-access-management-user-key-create.png) A window containing your Agent Memory service key will appear. Select **Copy** to copy the key to your clipboard. -{{The Agent Memory service key window. Use the Copy button to save the service key to the clipboard.}} +![The Agent Memory service key window. Use the Copy button to save the service key to the clipboard.](/images/rc/agent-memory-service-key.png) +{width="40%"} {{}} This is the only time the value of the user key is available. Save it to a secure location before closing the dialog box.

diff --git a/content/operate/iris/agent-memory/model-configuration.md b/content/operate/iris/agent-memory/model-configuration.md index 5745c74661..47aed42ff0 100644 --- a/content/operate/iris/agent-memory/model-configuration.md +++ b/content/operate/iris/agent-memory/model-configuration.md @@ -63,7 +63,7 @@ To configure your own model provider key: 1. Complete the other service settings, then select **Create**. -{{The AI model and credentials section with Bring my own key selected. The section contains the provider, API key, LLM model, and embedding model settings.}} +![The AI model and credentials section with Bring my own key selected. The section contains the provider, API key, LLM model, and embedding model settings.](/images/rc/agent-memory-ai-model-create.png) The key is used for both the LLM and embedding calls. Redis stores the key securely and does not show it again after you create the service. @@ -81,7 +81,7 @@ To view the configuration: 1. On the **Configuration** tab, find **AI model and credentials**. -{{The AI model and credentials section for an existing service. It shows the provider, embedding model, LLM model, and a User-managed API key status.}} +![The AI model and credentials section for an existing service. It shows the provider, embedding model, LLM model, and a User-managed API key status.](/images/rc/agent-memory-ai-model-details.png) The **User-managed** status confirms that the service uses your provider key. Redis does not display or return the saved value. @@ -99,7 +99,7 @@ To update the service: 1. Select **Save**. -{{The AI model and credentials section in edit mode. The provider and embedding model are read-only. The LLM model and Replace API key settings are editable.}} +![The AI model and credentials section in edit mode. The provider and embedding model are read-only. The LLM model and Replace API key settings are editable.](/images/rc/agent-memory-ai-model-edit.png) After the update completes, new operations use the replacement key. Operations that were already in progress can continue to use the previous key. The replacement applies to both LLM and embedding calls. diff --git a/content/operate/iris/agent-memory/view-service.md b/content/operate/iris/agent-memory/view-service.md index e03d93e1ca..219c154285 100644 --- a/content/operate/iris/agent-memory/view-service.md +++ b/content/operate/iris/agent-memory/view-service.md @@ -19,7 +19,7 @@ After you have [created your first Agent Memory service]({{< relref "/operate/ir This page displays a list of all Agent Memory services associated with your account. -{{The Agent Memory service in the Agent Memory service list.}} +![The Agent Memory service in the Agent Memory service list.](/images/rc/agent-memory-service-list.png) Select your Agent Memory service from the list to view the service's details. @@ -40,7 +40,7 @@ Some of these settings can be changed after service creation. To do so, select t The **General settings** section provides the connection details and general settings for your Agent Memory service. -{{The General settings for the Agent Memory service.}} +![The General settings for the Agent Memory service.](/images/rc/agent-memory-view-general.png) | Setting name |Description| |:----------------------|:----------| @@ -57,7 +57,7 @@ Follow the [Redis Agent Memory REST API quickstart]({{< relref "/develop/ai/cont The **Memory configuration** section shows the time-to-live (TTL) for memory storage, the extraction cadence, and the automatic summarization settings for session memory. -{{The Memory configuration section for the Agent Memory service.}} +![The Memory configuration section for the Agent Memory service.](/images/rc/agent-memory-view-memory-configuration.png) | Setting name |Description| |:----------------------|:----------| @@ -74,7 +74,7 @@ The **AI model and credentials** section appears when the service uses your mode Provider and model values shown in the screenshot are examples. -{{The AI model and credentials section for an existing service. It shows the provider, embedding model, LLM model, and a User-managed API key status.}} +![The AI model and credentials section for an existing service. It shows the provider, embedding model, LLM model, and a User-managed API key status.](/images/rc/agent-memory-ai-model-details.png) The provider and embedding model are read-only. You can change the LLM model or replace the provider key. For update steps, key rotation behavior, security, and troubleshooting guidance, see [Configure AI models for Agent Memory]({{< relref "/operate/iris/agent-memory/model-configuration" >}}). @@ -82,7 +82,7 @@ The provider and embedding model are read-only. You can change the LLM model or The **Memory types & extraction** section shows any [custom memory types]({{< relref "/operate/iris/agent-memory/create-service#custom-memory-types" >}}) defined for the service, each listed with its name, fields, and extraction strategy. -{{The Memory types & extraction section for the Agent Memory service.}} +![The Memory types & extraction section for the Agent Memory service.](/images/rc/agent-memory-view-memory-types.png) #### Custom memory types @@ -105,7 +105,7 @@ The **Sensitive-data exclusions** section shows the [sensitive-data exclusions]( Sensitive-data exclusions are an early-stage feature, enabled for selected accounts. If you want to try them, contact your Redis representative or [contact sales](https://redis.io/contact/). {{< /note >}} -{{The Sensitive-data exclusions section for the Agent Memory service.}} +![The Sensitive-data exclusions section for the Agent Memory service.](/images/rc/agent-memory-view-sensitive-data-exclusions.png) | Setting name |Description| |:----------------------|:----------| @@ -126,7 +126,7 @@ Semantic exclusions are **advisory**. They steer the extraction model, but they The **Actions** section lets you flush or delete your Agent Memory service. -{{The actions for the Agent Memory service.}} +![The actions for the Agent Memory service.](/images/rc/agent-memory-view-actions.png) #### Flush memory entries @@ -167,7 +167,7 @@ The **Metrics** tab provides a series of graphs showing performance data for you The **API keys** tab shows a list of all API keys for your service. -{{The actions for the Agent Memory service.}} +![The actions for the Agent Memory service.](/images/rc/agent-memory-view-api-keys.png) Here, you can generate a new API key or remove any keys that are no longer in use. You can generate or remove service API keys at any time. @@ -177,17 +177,20 @@ To generate a new service key: 1. Select **New API key**. - {{The New API key button.}} + ![The New API key button.](/images/rc/agent-memory-new-api-key.png) + {width="150px"} 1. Enter a new name for your API key. - {{The Add API key window.}} + ![The Add API key window.](/images/rc/agent-memory-add-api-key.png) + {width="37.5%"} 1. Select **Generate key** to generate your new API key. 1. The new key will appear in a dialog box. Select **Copy** to copy the key to the clipboard. - {{The Agent Memory service key window. Use the Copy button to save the service key to the clipboard.}} + ![The Agent Memory service key window. Use the Copy button to save the service key to the clipboard.](/images/rc/agent-memory-service-key.png) + {width="40%"} {{}} This is the only time the value of the user key is available. Save it to a secure location before closing the dialog box.

@@ -199,4 +202,5 @@ If you lose the service key value, you will need to generate a new key again. To delete an API key, select the **Delete API key** button next to the old key. -{{Delete button.}} +![Delete button.](/images/rc/icon-delete-lb.png) +{width="36px"} diff --git a/content/operate/iris/context-retriever/create-service.md b/content/operate/iris/context-retriever/create-service.md index f24556e0c6..013c784fa0 100644 --- a/content/operate/iris/context-retriever/create-service.md +++ b/content/operate/iris/context-retriever/create-service.md @@ -31,7 +31,8 @@ From the [Redis Cloud console](https://cloud.redis.io/), select **Context Retrie If you have not already created a Context Retriever service, you'll see a page with an introduction to Context Retriever. Otherwise, select **New service** to go to the Context Retriever introduction page. -{{The New service button.}} +![The New service button.](/images/rc/langcache-new-service.png) +{width="150px"} From here, you can either: @@ -44,7 +45,7 @@ For this guide, select **Create custom service**. The **General settings** section defines basic properties of your service. -{{The General settings section.}} +![The General settings section.](/images/rc/context-retriever-general-settings.png) | Setting name | Description | |:-------------|:------------| @@ -58,11 +59,11 @@ Select **Entities** to continue. In the **Define Entities** step, you'll define the objects that Context Retriever will use to generate retrieval tools. -{{The Entities section.}} +![The Entities section.](/images/rc/context-retriever-define-entities.png) Select **Add Entity** to add an entity. -{{The Entity table with the Entity Name, Key template, and description.}} +![The Entity table with the Entity Name, Key template, and description.](/images/rc/context-retriever-define-entities-table.png) - In the **Entity name** field, enter the name of one of the business objects that is in your database. @@ -94,11 +95,11 @@ If you use Auto-detect fields, make sure that the fields and relationships that - Select **Manually enter fields** to manually enter the fields yourself. -{{The Configure fields step.}} +![The Configure fields step.](/images/rc/context-retriever-fields.png) Expand each entry to view the currently defined fields for that entry. Select **Add field** to add a field. -{{The Add field table.}} +![The Add field table.](/images/rc/context-retriever-add-field.png) - Enter the field name in the **Field** cell. - Select the **PK** checkbox if the field is a primary key. You must have at least one primary key. diff --git a/content/operate/iris/context-retriever/view-admin-keys.md b/content/operate/iris/context-retriever/view-admin-keys.md index 99bdbb1436..22110a971d 100644 --- a/content/operate/iris/context-retriever/view-admin-keys.md +++ b/content/operate/iris/context-retriever/view-admin-keys.md @@ -21,7 +21,7 @@ A Context Retriever **admin key** authorizes administrative operations against C From the [Redis Cloud console](https://cloud.redis.io/), select **Context Retriever** from the left-hand menu, then select the **Admin keys** tab. -{{The Admin keys tab showing the list of admin keys.}} +![The Admin keys tab showing the list of admin keys.](/images/rc/context-retriever-admin-keys-list.png) This tab shows a list of all admin keys associated with Context Retriever in your account. Here, you can generate a new admin key or remove any keys that are no longer in use. You can generate or remove admin keys at any time. @@ -37,17 +37,20 @@ To generate a new admin key: 1. Select **New admin key**. - {{The New admin key button.}} + ![The New admin key button.](/images/rc/context-retriever-new-admin-key.png) + {width="150px"} 1. Enter a name for your admin key. - {{The Add admin key window.}} + ![The Add admin key window.](/images/rc/context-retriever-add-admin-key.png) + {width="37.5%"} 1. Select **Generate key** to generate your new admin key. 1. The new key will appear in a dialog box. Select **Copy** to copy the key to the clipboard. - {{The Context Retriever admin key window. Use the Copy button to save the admin key to the clipboard.}} + ![The Context Retriever admin key window. Use the Copy button to save the admin key to the clipboard.](/images/rc/context-retriever-admin-key.png) + {width="40%"} {{}} This is the only time the value of the admin key is available. Save it to a secure location before closing the dialog box.

@@ -59,6 +62,7 @@ If you lose the admin key value, you will need to generate a new admin key. To delete an admin key, select the **Delete admin key** button next to the key you want to remove. -{{Delete button.}} +![Delete button.](/images/rc/icon-delete-lb.png) +{width="36px"} Deleting an admin key immediately revokes any administrative operations that rely on it. This action cannot be undone. diff --git a/content/operate/iris/context-retriever/view-service.md b/content/operate/iris/context-retriever/view-service.md index c4ff56371f..9e9739e698 100644 --- a/content/operate/iris/context-retriever/view-service.md +++ b/content/operate/iris/context-retriever/view-service.md @@ -17,7 +17,7 @@ After you have [created your first Context Retriever service]({{< relref "/opera This page displays a list of all Context Retriever services associated with your account. -{{The Context Retriever service in the Context Retriever service list.}} +![The Context Retriever service in the Context Retriever service list.](/images/rc/context-retriever-service-list.png) Select your Context Retriever service from the list to view the service's details. @@ -34,7 +34,7 @@ The **Overview** tab lets you view the details of your Context Retriever service The **Details** section provides general settings for your Context Retriever service. -{{The General settings for the Context Retriever service.}} +![The General settings for the Context Retriever service.](/images/rc/context-retriever-view-details.png) | Setting name | Description | |:-------------|:------------| @@ -46,7 +46,7 @@ The **Details** section provides general settings for your Context Retriever ser The **Entities** section shows the entities, fields, and relationships that Context Retriever uses to generate retrieval tools. -{{The Entities section for the Context Retriever service.}} +![The Entities section for the Context Retriever service.](/images/rc/context-retriever-view-entities.png) Expand each entity to view its fields, primary keys, related entities, types, and indexes. @@ -54,7 +54,7 @@ Expand each entity to view its fields, primary keys, related entities, types, an The **Tools** section shows the tools that are available to your Agents. -{{The Entities section for the Context Retriever service.}} +![The Entities section for the Context Retriever service.](/images/rc/context-retriever-view-tools.png) You can use your Agents to call your tools. For more information, see the [Context Surfaces Python Client](https://pypi.org/project/redis-context-retriever/) @@ -62,7 +62,7 @@ You can use your Agents to call your tools. For more information, see the [Conte The **Actions** section lets you delete your Context Retriever service. -{{The actions for the Context Retriever service.}} +![The actions for the Context Retriever service.](/images/rc/context-retriever-view-actions.png) #### Delete service diff --git a/content/operate/iris/langcache/create-service.md b/content/operate/iris/langcache/create-service.md index 6b245fd8f9..9dc8635546 100644 --- a/content/operate/iris/langcache/create-service.md +++ b/content/operate/iris/langcache/create-service.md @@ -37,17 +37,20 @@ From the [Redis Cloud console](https://cloud.redis.io/), select **LangCache** fr If you have not already created a LangCache service, you'll see a page with an introduction to LangCache. Otherwise, select **New service** to go to the LangCache introduction page. -{{The New service button.}} +![The New service button.](/images/rc/langcache-new-service.png) +{width="150px"} From here: - Select **Quick create** to create a LangCache service with default settings using your Free 30MB database. If you haven't created a Free database yet, Redis Cloud will create one and set up the LangCache service for you. - {{The Quick create button.}} + ![The Quick create button.](/images/rc/langcache-quick-create.png) + {width="150px"} After Redis Cloud creates your LangCache service, a window containing your LangCache service key will appear. Select **Copy** to copy the key to your clipboard. - {{The LangCache service key window. Use the Copy button to save the service key to the clipboard.}} + ![The LangCache service key window. Use the Copy button to save the service key to the clipboard.](/images/rc/langcache-service-key.png) + {width="37.5%"} {{}} This is the only time the value of the user key is available. Save it to a secure location before closing the dialog box.

@@ -61,7 +64,8 @@ If you lose the service key value, you will need to [generate a new service key] - If you want to customize your LangCache service, select **Create custom service**. - {{The Create custom service button.}} + ![The Create custom service button.](/images/rc/langcache-custom-service.png) + {width="150px"} This takes you to the **Create LangCache service** page. The page is divided into the following sections: @@ -73,7 +77,7 @@ If you lose the service key value, you will need to [generate a new service key] The **General settings** section defines basic properties of your service. -{{The General settings section.}} +![The General settings section.](/images/rc/langcache-general-settings.png) | Setting name |Description| |:----------------------|:----------| @@ -86,7 +90,7 @@ The **General settings** section defines basic properties of your service. The **Embedding settings** section defines the embedding model used by your service. -{{The Embedding settings section.}} +![The Embedding settings section.](/images/rc/langcache-embedding-settings.png) Required settings depend on the embedding provider you select. @@ -104,35 +108,39 @@ Attributes provide powerful scoping capabilities for your LangCache operations. The **Attributes settings** section allows you to define attributes for your service. It is collapsed by default. -{{The Attributes settings section.}} +![The Attributes settings section.](/images/rc/langcache-attribute-settings.png) LangCache allows you to define up to 5 custom attributes that align with your specific use case. To add a new attribute: 1. Select **Add attribute**. - {{The Add attribute button.}} + ![The Add attribute button.](/images/rc/langcache-add-attribute.png) + {width="150px"} 1. Give your custom attribute a descriptive name and select the check mark button to save it. - {{The custom attributes section. Select the Confirm add attribute button to save your attribute.}} + ![The custom attributes section. Select the Confirm add attribute button to save your attribute.](/images/rc/langcache-custom-attributes.png) After you save your custom attribute, it will appear in the list of custom attributes. Use the **Delete** button to remove it. -{{Select the Delete button to delete the selected attribute.}} +![Select the Delete button to delete the selected attribute.](/images/rc/icon-delete-lb.png) +{width="36px"} You can also select **Add attribute** again to add an additional attribute. -{{The Add attribute button.}} +![The Add attribute button.](/images/rc/langcache-add-attribute.png) +{width="150px"} ### Create service When you are done setting the details of your LangCache service, select **Create** to create it. -{{Use the Create button to create a LangCache service.}} +![Use the Create button to create a LangCache service.](/images/rc/button-access-management-user-key-create.png) A window containing your LangCache service key will appear. Select **Copy** to copy the key to your clipboard. -{{The LangCache service key window. Use the Copy button to save the service key to the clipboard.}} +![The LangCache service key window. Use the Copy button to save the service key to the clipboard.](/images/rc/langcache-service-key.png) +{width="37.5%"} {{}} This is the only time the value of the user key is available. Save it to a secure location before closing the dialog box.

@@ -142,7 +150,7 @@ If you lose the service key value, you will need to [generate a new service key] You'll be taken to your LangCache service's **Configuration** page. You'll also be able to see your LangCache service in the LangCache service list. -{{The LangCache service in the LangCache service list.}} +![The LangCache service in the LangCache service list.](/images/rc/langcache-service-list.png) If an error occurs, verify that: - Your database is active. diff --git a/content/operate/iris/langcache/monitor-cache.md b/content/operate/iris/langcache/monitor-cache.md index 17c79f2578..b2b4006361 100644 --- a/content/operate/iris/langcache/monitor-cache.md +++ b/content/operate/iris/langcache/monitor-cache.md @@ -16,7 +16,7 @@ aliases: You can monitor a LangCache service's performance from the **Metrics** tab of the service's page. -{{The metrics tab of the LangCache service's page.}} +![The metrics tab of the LangCache service's page.](/images/rc/langcache-metrics.png) The **Metrics** tab provides a series of graphs showing performance data for your LangCache service. diff --git a/content/operate/iris/langcache/view-edit-cache.md b/content/operate/iris/langcache/view-edit-cache.md index 27c57da129..4f03187f01 100644 --- a/content/operate/iris/langcache/view-edit-cache.md +++ b/content/operate/iris/langcache/view-edit-cache.md @@ -18,7 +18,7 @@ After you have [created your first LangCache service]({{< relref "/operate/iris/ This page displays a list of all LangCache services associated with your account. -{{The LangCache service in the LangCache service list.}} +![The LangCache service in the LangCache service list.](/images/rc/langcache-service-list.png) Select your LangCache service from the list to view the service's details. @@ -34,7 +34,7 @@ The **Configuration** tab lets you view the details of your LangCache service. I The **Connectivity** section provides the connection details for your LangCache service. -{{The connectivity settings for the LangCache service.}} +![The connectivity settings for the LangCache service.](/images/rc/langcache-view-connectivity.png) | Setting name |Description| |:----------------------|:----------| @@ -54,13 +54,14 @@ To generate a new service key: 1. Select **Generate key**. - {{The Generate Key button.}} + ![The Generate Key button.](/images/rc/langcache-replace-key.png) 1. A confirmation dialog will appear. Select **Confirm** to confirm. 1. The new key will appear in a dialog box. Select **Copy** to copy the key to the clipboard. - {{The LangCache service key window. Use the Copy button to save the service key to the clipboard.}} + ![The LangCache service key window. Use the Copy button to save the service key to the clipboard.](/images/rc/langcache-service-key.png) + {width="37.5%"} {{}} After you generate a new service key, calls to the LangCache API with the old key will fail.

@@ -74,7 +75,7 @@ If you lose the service key value, you will need to generate a new key again. The **General** section provides configuration details for your LangCache service. -{{The general settings for the LangCache service.}} +![The general settings for the LangCache service.](/images/rc/langcache-view-general.png) | Setting name |Description| |:----------------------|:----------| @@ -92,7 +93,7 @@ Some of these settings can be changed after cache creation. To do so, select the The **Attributes** section provides the custom attributes defined for your LangCache service. -{{The custom attributes for the LangCache service.}} +![The custom attributes for the LangCache service.](/images/rc/langcache-view-attributes.png) You can not edit custom attributes after cache creation. @@ -100,7 +101,7 @@ You can not edit custom attributes after cache creation. The **Actions** section lets you flush or delete your LangCache service. -{{The actions for the LangCache service.}} +![The actions for the LangCache service.](/images/rc/langcache-view-actions.png) #### Flush cache diff --git a/content/operate/radar/agent.md b/content/operate/radar/agent.md index ee671e5ca8..26a775e6d2 100644 --- a/content/operate/radar/agent.md +++ b/content/operate/radar/agent.md @@ -91,7 +91,8 @@ Run every agent command as the service identity, as `sudo -u mcm /usr/libexec/mc Radar shows an activation command and a daemon command. - {{The Activate managed agent dialog, showing the activation command and the daemon command}} + ![The Activate managed agent dialog, showing the activation command and the daemon command](/images/radar/activate-managed-agent.png) + {width="75%"}
@@ -115,7 +116,8 @@ Run every agent command as the service identity, as `sudo -u mcm /usr/libexec/mc 3. In Radar, find the request under **Pending activations**, confirm the activation code matches, and select **Approve**. - {{The Agents tab, showing pending activations with Approve and Deny actions above the registered agents list}} + ![The Agents tab, showing pending activations with Approve and Deny actions above the registered agents list](/images/radar/settings-agents.png) + {width="90%"} The activation expires 15 minutes after the command prints the code, so approve it while the command is still waiting. @@ -157,7 +159,8 @@ Managed mode stores the credential it was issued in `/var/lib/radar-agent/agent- Manage these tokens later under **Settings > Access keys**. - {{The Access keys tab, listing credential keys with their creation date, last use, and Revoke action}} + ![The Access keys tab, listing credential keys with their creation date, last use, and Revoke action](/images/radar/settings-access-keys.png) + {width="90%"}
@@ -317,7 +320,8 @@ The exported file holds sanitized telemetry only. It never contains your Radar t Every agent appears in Radar under **Settings > Agents** and in the **Connected agents** list on the Connections page. Radar shows each agent's mode, platform, version, and last heartbeat, along with the combined health of the sources it collects from. -{{The Connections page, with the Connected agents list showing each agent's mode, platform, version, and status}} +![The Connections page, with the Connected agents list showing each agent's mode, platform, version, and status](/images/radar/connections-with-agents.png) +{width="90%"} To expose health and metrics endpoints on the agent host, pass `--metrics-addr` when you start the daemon: diff --git a/content/operate/radar/connect.md b/content/operate/radar/connect.md index 4f63f125ab..df3ca6dc73 100644 --- a/content/operate/radar/connect.md +++ b/content/operate/radar/connect.md @@ -24,7 +24,8 @@ After installing Redis Radar, it's time to connect your clusters. Add each clust Radar encrypts every credential before storing it. Credentials are never returned through the API and never written to logs. -{{The Add connection dialog, with the connection type selector open}} +![The Add connection dialog, with the connection type selector open](/images/radar/add-connection.png) +{width="75%"} ## Self-managed connections @@ -53,7 +54,8 @@ Radar tests the connection before it saves anything. If the test fails, Radar sh Radar always reaches the REST API over HTTPS. -{{The Add connection dialog set to connection type Redis Software}} +![The Add connection dialog set to connection type Redis Software](/images/radar/add-connection-redis-software.png) +{width="75%"} {{< note >}} Point Radar at the cluster's fully qualified domain name rather than one node's address. A node address works until that node is unavailable, at which point Radar reports the whole cluster as unreachable. @@ -71,7 +73,8 @@ Radar connects straight to the instance, so it needs network access to that endp 6. Select **Use TLS (rediss://)** if the instance requires an encrypted connection. 7. Select **Add connection**. -{{The Add connection dialog set to connection type Redis Open Source}} +![The Add connection dialog set to connection type Redis Open Source](/images/radar/add-connection-redis-open-source.png) +{width="75%"} ## Cloud connections @@ -96,7 +99,8 @@ A Redis Cloud connection uses the Redis Cloud API, so it covers every subscripti 5. Enter the **account key** and the **user secret**. 6. Select **Add connection**. -{{The Add connection dialog set to connection type Redis Cloud}} +![The Add connection dialog set to connection type Redis Cloud](/images/radar/add-connection-redis-cloud.png) +{width="75%"} ### Connect Amazon ElastiCache @@ -148,7 +152,8 @@ Radar derives the AWS account ID itself, so you do not enter it. Both the API server and the worker need outbound HTTPS on port 443 to the AWS control-plane endpoints in every region you configure: `sts`, `elasticache`, `monitoring`, `tagging`, and `ec2`. Radar never opens a connection to a cache endpoint. -{{The Add connection dialog set to connection type Amazon ElastiCache}} +![The Add connection dialog set to connection type Amazon ElastiCache](/images/radar/add-connection-amazon-elasticache.png) +{width="75%"} {{< note >}} Blocking the CloudWatch or tagging endpoints degrades what Radar can report and produces a capability warning. Blocking the identity or ElastiCache inventory endpoints stops the connection test and collection outright. @@ -206,7 +211,8 @@ On a self-managed install, Radar authenticates with a service account key: Both the API server and the worker need outbound HTTPS on port 443 to `oauth2.googleapis.com`, `redis.googleapis.com`, `memorystore.googleapis.com`, `memcache.googleapis.com`, and `monitoring.googleapis.com`. Allowing `*.googleapis.com` covers the whole path. -{{The Add connection dialog set to connection type Google Memorystore}} +![The Add connection dialog set to connection type Google Memorystore](/images/radar/add-connection-google-memorystore.png) +{width="75%"} ## Secure cluster connections diff --git a/content/operate/radar/licenses-and-certificates.md b/content/operate/radar/licenses-and-certificates.md index ccba57a73b..410a00f1bd 100644 --- a/content/operate/radar/licenses-and-certificates.md +++ b/content/operate/radar/licenses-and-certificates.md @@ -36,7 +36,8 @@ Radar also shows a fleet-wide total, so you can see aggregate headroom without a A license changed on the cluster shows up in Radar at its next collection. -{{The Licenses page, listing clusters by license status, expiration date, and shard usage}} +![The Licenses page, listing clusters by license status, expiration date, and shard usage](/images/radar/licenses.png) +{width="90%"} ## Certificates @@ -44,7 +45,8 @@ The **Certificates** view lists each cluster's certificates by type, with the ex A certificate renewed on the cluster shows up in Radar with its new expiration date at the next collection. -{{The Certificates page, listing certificates by type, cluster, and expiration date}} +![The Certificates page, listing certificates by type, cluster, and expiration date](/images/radar/certificates.png) +{width="90%"} ## Next steps diff --git a/content/operate/radar/manage-access.md b/content/operate/radar/manage-access.md index f536a7847f..87ad8f0d4e 100644 --- a/content/operate/radar/manage-access.md +++ b/content/operate/radar/manage-access.md @@ -16,7 +16,8 @@ Radar has two roles, administrator and viewer, one of which is assigned to every Create local accounts under **Users**. Choose and configure the sign-in method under **Settings > Authentication**, where that choice applies to all of Radar. -{{The Settings > Authentication page, showing the Application, SAML, and LDAP method selector}} +![The Settings > Authentication page, showing the Application, SAML, and LDAP method selector](/images/radar/settings-authentication.png) +{width="75%"} ## Roles @@ -38,7 +39,8 @@ New users are viewers unless you choose otherwise. Only admins can see or change The **Users** list shows each account's role, where it authenticates, when it was created, and its last sign-in, so you can tell a local account from a directory account at a glance. -{{The Users page, listing a local account with its role, status, and last login}} +![The Users page, listing a local account with its role, status, and last login](/images/radar/users.png) +{width="90%"} If an account locks, admins unlock it from the same list. diff --git a/content/operate/radar/monitor.md b/content/operate/radar/monitor.md index 10516a6caa..e357c1f0e3 100644 --- a/content/operate/radar/monitor.md +++ b/content/operate/radar/monitor.md @@ -51,7 +51,8 @@ The **Overview** answers one question for a fleet too large to check by hand: is - **Alerts.** The most severe alerts currently raised. See [Alerts](#alerts). - **Running actions.** Operations in progress on your clusters. -{{The Radar Overview page, showing fleet status, inventory, database health, and alerts}} +![The Radar Overview page, showing fleet status, inventory, database health, and alerts](/images/radar/overview.png) +{width="90%"} ## Clusters @@ -74,13 +75,15 @@ The **Clusters** list is one row per cluster, whichever deployment type it came Sort by **Name** or **Memory**; the other columns are display-only. -{{The Radar Clusters page, listing clusters with their type, status, memory, and database counts}} +![The Radar Clusters page, listing clusters with their type, status, memory, and database counts](/images/radar/clusters.png) +{width="90%"} Select any cluster to open its detail view, which carries that cluster's nodes, databases, and configuration. For Redis Software clusters, select a row's **More options** menu and choose **Open cluster UI** to jump straight to that cluster's own management console in a new tab. -{{A cluster detail view for a Redis Software cluster, showing its overview, nodes, databases, and alerts}} +![A cluster detail view for a Redis Software cluster, showing its overview, nodes, databases, and alerts](/images/radar/cluster-detail-enterprise.png) +{width="90%"} ## Databases @@ -97,11 +100,13 @@ The **Databases** list crosses cluster boundaries, so you can find a database wi | Memory | Memory in use. | | Last Seen | When Radar last collected this database's state. | -{{The Radar Databases page, listing databases across clusters with their type, status, and version}} +![The Radar Databases page, listing databases across clusters with their type, status, and version](/images/radar/databases.png) +{width="90%"} Select a database to open its detail view. -{{A database detail view for a Redis Software database}} +![A database detail view for a Redis Software database](/images/radar/database-detail-enterprise.png) +{width="90%"} ### Active-Active databases @@ -130,7 +135,8 @@ Radar reads alerts from each cluster's own alert endpoints, at the cluster and n Filter by severity or search by alert, cluster, or FQDN. Select the cluster name in an alert to open that cluster's detail view. -{{The Radar Alerts page, listing alerts by severity, category, and affected resource}} +![The Radar Alerts page, listing alerts by severity, category, and affected resource](/images/radar/alerts.png) +{width="90%"} ## Download a support package diff --git a/content/operate/redisinsight/proxy.md b/content/operate/redisinsight/proxy.md index ea7e9b2556..02fb4dad0e 100644 --- a/content/operate/redisinsight/proxy.md +++ b/content/operate/redisinsight/proxy.md @@ -94,10 +94,10 @@ server { ### Login page -{{< image filename="/images/ri/ri-reverse-proxy-login.png" alt="RedisInsight login page" >}} +![RedisInsight login page](/images/ri/ri-reverse-proxy-login.png) ### After login -{{< image filename="/images/ri/ri-reverse-proxy-post-login.png" alt="RedisInsight after login" >}} +![RedisInsight after login](/images/ri/ri-reverse-proxy-post-login.png)