diff --git a/content/integrate/amazon-bedrock/create-agent.md b/content/integrate/amazon-bedrock/create-agent.md index f064b392f6..0b4e9e032b 100644 --- a/content/integrate/amazon-bedrock/create-agent.md +++ b/content/integrate/amazon-bedrock/create-agent.md @@ -35,7 +35,8 @@ Before you begin this guide, you will need: 1. Select **Agents** > **Create Agent** to create your knowledge base. - {{The Create Agent button.}} + ![The Create Agent button.](/images/rc/bedrock-aws-button-create-agent.png) + {width="150px"} 1. In the **Agent name** section, enter a name and description for your agent. @@ -51,18 +52,21 @@ Before you begin this guide, you will need: 1. Select the [knowledge base](#create-a-knowledge-base) you created and summarize the information in the knowledge base in the **Knowledge base instructions for Agent** form. Select **Add another knowledge base** if you would like to add multiple knowledge bases. - {{The Add another knowledge base button.}} + ![The Add another knowledge base button.](/images/rc/bedrock-aws-button-add-knowledge-base.png) + {width="400px"} Select **Next** to continue. 1. Review your agent before you create it. Select **Create Agent** to finish creation. - {{The Create Agent button.}} + ![The Create Agent button.](/images/rc/bedrock-aws-button-create-agent.png) + {width="150px"} Amazon Bedrock will create your agent and link it to your knowledge base. This will take some time. Your agent will have a status of **Ready** when it is ready to be tested. -{{A Bedrock agent with a Ready status.}} +![A Bedrock agent with a Ready status.](/images/rc/bedrock-aws-status-agent-ready.png) +{width="75%"} Select the name of your agent to view the versions and draft aliases of your agent. You can also test your agent by entering prompts in the **Enter your message here** field. \ No newline at end of file diff --git a/content/integrate/amazon-bedrock/create-knowledge-base.md b/content/integrate/amazon-bedrock/create-knowledge-base.md index 222ffb9a16..374c8f6d23 100644 --- a/content/integrate/amazon-bedrock/create-knowledge-base.md +++ b/content/integrate/amazon-bedrock/create-knowledge-base.md @@ -39,7 +39,8 @@ To use your Redis database to create a knowledge base on Amazon Bedrock: 1. Select **Knowledge base** > **Create knowledge base** to create your knowledge base. - {{The Create knowledge base button.}} + ![The Create knowledge base button.](/images/rc/bedrock-aws-button-create-knowledge-base.png) + {width="200px"} 1. In the **Knowledge base details** section, enter a name and description for your knowledge base. @@ -49,7 +50,8 @@ To use your Redis database to create a knowledge base on Amazon Bedrock: 1. In the **Vector database** section, select **Redis Cloud** and select the checkbox to agree with the legal disclaimer. - {{The Redis Cloud selection for your vector database.}} + ![The Redis Cloud selection for your vector database.](/images/rc/bedrock-aws-select-redis-vector-db.png) + {width="500px"} Fill in the fields with the following information: @@ -64,16 +66,19 @@ To use your Redis database to create a knowledge base on Amazon Bedrock: 1. Review your knowledge base before you create it. Select **Create knowledge base** to finish creation. - {{The Create knowledge base button.}} + ![The Create knowledge base button.](/images/rc/bedrock-aws-button-create-knowledge-base.png) + {width="200px"} Amazon Bedrock will sync the data from the S3 bucket and load it into your Redis database. This will take some time. Your knowledge base will have a status of **Ready** when it is ready to be connected to an Agent. -{{A Bedrock knowledge base with a Ready status.}} +![A Bedrock knowledge base with a Ready status.](/images/rc/bedrock-aws-status-knowledge-base-ready.png) +{width="500px"} Select the name of your knowledge base to view the syncing status of your data sources. The data source will have a status of **Ready** when it is synced to the vector database. -{{A Bedrock data source with a Ready status.}} +![A Bedrock data source with a Ready status.](/images/rc/bedrock-aws-status-data-source-ready.png) +{width="600px"} After the knowledge base is ready, you can use it to [Create an agent](/content/integrate/amazon-bedrock/create-agent.md). diff --git a/content/integrate/amazon-bedrock/set-up-redis.md b/content/integrate/amazon-bedrock/set-up-redis.md index a9dc0d4cb6..a05e5ce654 100644 --- a/content/integrate/amazon-bedrock/set-up-redis.md +++ b/content/integrate/amazon-bedrock/set-up-redis.md @@ -39,23 +39,26 @@ To set up a Redis Cloud instance for Bedrock, you need to: 1. Select the [Redis Cloud](https://aws.amazon.com/marketplace/pp/prodview-mwscixe4ujhkq?sr=0-1&ref_=beagle&applicationId=AWSMPContessa) AWS marketplace link from Bedrock to be taken to the Redis Cloud plan listing. - {{The Redis Cloud listing on AWS Marketplace}} + ![The Redis Cloud listing on AWS Marketplace](/images/rc/aws-marketplace-rc-listing.png) 1. Subscribe to Redis Cloud listing, locate the **Set Up Your Account** button, and then select it to begin mapping your Redis Cloud account with your AWS Marketplace account. - {{Use the Set Up Your Account button after subscribing to Redis Cloud with your AWS Marketplace account.}} + ![Use the Set Up Your Account button after subscribing to Redis Cloud with your AWS Marketplace account.](/images/rc/aws-marketplace-account-setup-button.png) + {width="50%"} 1. Sign in to the [Redis Cloud console](https://cloud.redis.io). 1. Select the Redis account to be mapped to your AWS Marketplace account and confirm that your payment method will change and that the connection cannot be undone. - {{Use the AWS Marketplace dialog to map your Redis Cloud account to your AWS Marketplace account.}} + ![Use the AWS Marketplace dialog to map your Redis Cloud account to your AWS Marketplace account.](/images/rc/aws-marketplace-map-account-dialog.png) + {width="80%"} 1. Use the **Map account** button to confirm your choice. 1. Once your Redis account is mapped to your AWS Marketplace account, a message appears in the upper, left corner of the account panel. - {{The AWS Marketplace badge appears when your Redis Cloud account is mapped to an AWS Marketplace account.}} + ![The AWS Marketplace badge appears when your Redis Cloud account is mapped to an AWS Marketplace account.](/images/rc/aws-marketplace-billing-badge.png) + {width="150px"} In addition, AWS Marketplace is reported as the selected payment method. @@ -63,27 +66,29 @@ To set up a Redis Cloud instance for Bedrock, you need to: 1. In the [Redis Cloud console](https://cloud.redis.io/), select **New database**. - {{The New Database button creates a new database.}} + ![The New Database button creates a new database.](/images/rc/button-database-new.png) + {width="120px"} 1. When the **New database** page appears, select **Pro** to create a Pro plan. - {{The Subscription selection panel with Pro selected.}} + ![The Subscription selection panel with Pro selected.](/images/rc/create-database-subscription-pro-new.png) 1. After you select **Pro**, the **Database settings** section will appear. For this guide, continue with **Easy create** to get started faster. - {{The database settings section.}} + ![The database settings section.](/images/rc/create-pro-db-settings.png) If you'd like to select all of the configuration options yourself, select **Custom settings**. See [Create a Redis Cloud Pro database](/content/operate/rc/databases/create-database/create-pro-database-new.md#custom-settings) for more details. 1. Redis will generate a database name for you. If you want to change it, you can do so in the **Database name** field. - {{The database name, cloud vendor and region settings.}} + ![The database name, cloud vendor and region settings.](/images/rc/pro-easy-create-vendor.png) + {width="75%"} 1. Select **Amazon Web Services** as the cloud vendor and select a region. 1. In the **Database Sizing** section: - {{The Dataset size, throughput, and High availability settings.}} + ![The Dataset size, throughput, and High availability settings.](/images/rc/pro-easy-create-size-throughput.png) - Select [**High availability**](/content/operate/rc/databases/configuration/high-availability.md) if it is not already selected. - Set the Dataset size of your database based on the amount of data that Bedrock will pull from your Simple Storage Service (S3) [bucket](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html). See [Find out the size of your S3 buckets](https://aws.amazon.com/blogs/storage/find-out-the-size-of-your-amazon-s3-buckets/) to find out how much knowledge base data is stored in your S3 bucket and pick the closest size, rounded up, from the table below. @@ -99,13 +104,14 @@ To set up a Redis Cloud instance for Bedrock, you need to: 1. Select **View all settings** to review the database settings that we selected for you. - {{The optimal database settings.}} + ![The optimal database settings.](/images/rc/pro-easy-create-optimal-settings.png) If you want to change these settings, select [**Switch to custom settings**](/content/operate/rc/databases/create-database/create-pro-database-new.md#custom-settings). 1. You will not need to enter a payment method, as it's automatically assigned to your AWS Marketplace account. Select **Confirm & pay** to create your new database. - {{Select Confirm & pay to create your new database.}} + ![Select Confirm & pay to create your new database.](/images/rc/button-create-db-confirm-pay.png) + {width="140px"} Note that databases are created in the background. While they are provisioning, you aren't allowed to make changes. (The process generally takes 10-15 minutes.) @@ -119,29 +125,33 @@ For your database to be fully secure, you must enable [Transport Layer Security 1. From the database's **Configuration** screen, select the **Edit** button: - {{The Edit database button lets you change selected database properties.}} + ![The Edit database button lets you change selected database properties.](/images/rc/button-database-edit.png) + {width="100px"} 1. In the **Security** section, use the **Transport layer security (TLS)** toggle to enable TLS: - {{Use the Transport Layer Security toggle to enable TLS.}} + ![Use the Transport Layer Security toggle to enable TLS.](/images/rc/database-details-configuration-tab-security-tls-toggle.png) + {width="200px"} 1. Select **Download server certificate** to download the Redis Cloud certificate bundle `redis_ca.pem`: - {{Use the Download server certificate button to download the Redis Cloud CA certificates.}} + ![Use the Download server certificate button to download the Redis Cloud CA certificates.](/images/rc/button-database-config-security-server-ca-download.png) + {width="250px"} 1. Select the **Mutual TLS (require client authentication)** checkbox to require client authentication. 1. Select **Add client certificate** to add a certificate. - {{The Add client certificate button.}} + ![The Add client certificate button.](/images/rc/mtls-add-client-certificate.png) + {width="200px"} 1. Either provide an [X.509 client certificate](https://en.wikipedia.org/wiki/X.509) or chain in PEM format for your client or select **Generate** to create one: - {{Provide or generate a certificate for Mutual TLS.}} + ![Provide or generate a certificate for Mutual TLS.](/images/rc/database-details-configuration-tab-security-tls-client-auth-certificate.png) - If you generate your certificate from the Redis Cloud console, a **Download certificate** button will appear after it is generated. Select it to download the certificate. - {{The Download certificate button.}} + ![The Download certificate button.](/images/rc/mtls-download-certificate.png) The download contains: @@ -154,11 +164,12 @@ For your database to be fully secure, you must enable [Transport Layer Security - If you provide a client certificate, you will see the certificate details before you save your changes. - {{The Download certificate button.}} + ![The Download certificate button.](/images/rc/mtls-certificate-details.png) 1. To apply your changes and enable TLS, select the **Save database** button: - {{Use the Save database button to save database changes.}} + ![Use the Save database button to save database changes.](/images/rc/button-database-save.png) + {width="140px"} ## Store database credentials in AWS secrets manager {#store-secret} @@ -186,23 +197,26 @@ To create your vector index in Redis Insight: 1. In the [Redis Cloud console](https://cloud.redis.io/), in your database's **Configuration** tab, select the **Connect** button next to your database to open the connection wizard. - {{< image filename="/images/rc/button-connect.png#no-click" alt="Connect button." >}} + ![Connect button.](/images/rc/button-connect.png#no-click) 1. In the connection wizard, under **Redis Insight Desktop**, select **Public Endpoint**. Select **Open with Redis Insight** to connect to the database with Redis Insight. 1. Select **Use TLS**. In the **CA Certificate** section, select **Add new CA certificate**. Give the certificate a name in the **Name** field, and enter the contents of `redis_ca.pem` into the **Certificate** field. - {{The Redis Insight Add CA Certificate section.}} + ![The Redis Insight Add CA Certificate section.](/images/rc/ri-bedrock-add-ca-cert.png) + {width="80%"} 1. Select **Requires TLS Client Authentication**. In the **Client Certificate** section, select **Add new certificate**. Give the certificate a name in the **Name** field. Enter the contents of `redis_user.crt` into the **Certificate** field, and the contents of `redis_user_private.key` into the **Private Key** field. - {{The Redis Insight Add Client Certificate section.}} + ![The Redis Insight Add Client Certificate section.](/images/rc/ri-bedrock-add-client-cert.png) + {width="80%"} 1. Select **Add Redis Database** to connect to the database. 1. Select your database alias to connect to your database. Select the **Workbench** icon to go to the workbench. - {{The Redis Insight workbench icon.}} + ![The Redis Insight workbench icon.](/images/rc/ri-bedrock-workbench.png) + {width="50px"} 1. Enter the [FT.CREATE](/content/commands/ft.create.md) command to create an index. @@ -228,7 +242,8 @@ To create your vector index in Redis Insight: 1. Select **Run** to create the index. - {{The Redis Insight run button.}} + ![The Redis Insight run button.](/images/rc/ri-bedrock-run-button.png) + {width="50px"} ### `redis-cli` diff --git a/content/integrate/confluent-with-redis-cloud/_index.md b/content/integrate/confluent-with-redis-cloud/_index.md index a7cd237449..881764673c 100644 --- a/content/integrate/confluent-with-redis-cloud/_index.md +++ b/content/integrate/confluent-with-redis-cloud/_index.md @@ -52,11 +52,11 @@ To add the Redis Sink connector to your Confluent Cloud environment from the Red 1. Select the **Configure** button in the **Confluent** tile. - {{The Confluent integration tile.}} + ![The Confluent integration tile.](/images/rc/account-settings-integrations-confluent.png) 1. This will take you to [New Sink Connector](https://confluent.cloud/go/new-sink-connector/RedisSink) on Confluent Cloud. If you have more than one Confluent Cloud environment or Cluster, select your environment and cluster from the lists and select **Continue**. - {{Select your environment and cluster from the Create a Connector selector.}} + ![Select your environment and cluster from the Create a Connector selector.](/images/rc/confluent-create-connector.png) 1. From there, follow the steps to [Enter the connector details](https://docs.confluent.io/cloud/current/connectors/cc-redis-sink.html#step-4-enter-the-connector-details) on the Confluent documentation. diff --git a/content/integrate/datadog-with-redis-cloud/_index.md b/content/integrate/datadog-with-redis-cloud/_index.md index 4854440a4a..4aa84101ed 100644 --- a/content/integrate/datadog-with-redis-cloud/_index.md +++ b/content/integrate/datadog-with-redis-cloud/_index.md @@ -34,7 +34,7 @@ This integration makes it possible to: - Set up automatic alerts for node or cluster events - Display these metrics alongside data from other systems -{{< image filename="/images/rc/redis-cloud-datadog.png" alt="screenshot of datadog dashboard">}} +![screenshot of datadog dashboard](/images/rc/redis-cloud-datadog.png) ## Install Redis' Datadog Integration for Redis Cloud Installing the Datadog integration is a two-step process. Firstly, the installation must be part of your configuration. diff --git a/content/integrate/datadog-with-redis-enterprise/_index.md b/content/integrate/datadog-with-redis-enterprise/_index.md index 92d61e4db8..dad394bf1f 100644 --- a/content/integrate/datadog-with-redis-enterprise/_index.md +++ b/content/integrate/datadog-with-redis-enterprise/_index.md @@ -34,7 +34,7 @@ This integration makes it possible to: - Set up automatic alerts for node or cluster events - Display these metrics alongside data from other systems -{{< image filename="/images/rc/redis-cloud-datadog.png" >}} +![](/images/rc/redis-cloud-datadog.png) ## Install Redis' Datadog Integration for Redis Software Installing the Datadog integration is a two-step process. Firstly, the installation must be part of your configuration. diff --git a/content/integrate/dynatrace-with-redis-cloud/_index.md b/content/integrate/dynatrace-with-redis-cloud/_index.md index 7fbe8c45e2..bf6599daec 100644 --- a/content/integrate/dynatrace-with-redis-cloud/_index.md +++ b/content/integrate/dynatrace-with-redis-cloud/_index.md @@ -31,7 +31,7 @@ This integration makes it possible to: - Set up automatic alerts for node or cluster events - Display these metrics alongside data from other systems -{{< image filename="/images/rc/redis-cloud-dynatrace.png" >}} +![](/images/rc/redis-cloud-dynatrace.png) ## Install Redis' Dynatrace Integration for Redis Cloud The Dynatrace Integration is based on a feature of the Prometheus data source. Prometheus can forward metrics on to diff --git a/content/integrate/dynatrace-with-redis-enterprise/_index.md b/content/integrate/dynatrace-with-redis-enterprise/_index.md index 28002073a7..a82e7e1ab7 100644 --- a/content/integrate/dynatrace-with-redis-enterprise/_index.md +++ b/content/integrate/dynatrace-with-redis-enterprise/_index.md @@ -32,7 +32,7 @@ This integration makes it possible to: - Set up automatic alerts for node or cluster events - Display these metrics alongside data from other systems -{{< image filename="/images/rs/redis-enterprise-dynatrace.png" >}} +![](/images/rs/redis-enterprise-dynatrace.png) ## Install Redis' Dynatrace Integration for Redis Software At the present time the Dynatrace integration is not signed by Dynatrace, meaning that it will be necessary to download diff --git a/content/integrate/new-relic-with-redis-cloud/_index.md b/content/integrate/new-relic-with-redis-cloud/_index.md index 7ac06da08f..8dc30c1e3c 100644 --- a/content/integrate/new-relic-with-redis-cloud/_index.md +++ b/content/integrate/new-relic-with-redis-cloud/_index.md @@ -32,7 +32,7 @@ This integration makes it possible to: - Set up automatic alerts for node or cluster events - Display these metrics alongside data from other systems -{{< image filename="/images/rc/redis-cloud-newrelic.png" >}} +![](/images/rc/redis-cloud-newrelic.png) ## Install Redis' New Relic Integration for Redis Cloud The New Relic Integration for Redis is based on a feature of the Prometheus data source. Prometheus can forward metrics on to diff --git a/content/integrate/new-relic-with-redis-enterprise/_index.md b/content/integrate/new-relic-with-redis-enterprise/_index.md index cfada50085..2c1058a165 100644 --- a/content/integrate/new-relic-with-redis-enterprise/_index.md +++ b/content/integrate/new-relic-with-redis-enterprise/_index.md @@ -32,7 +32,7 @@ This integration makes it possible to: - Set up automatic alerts for node or cluster events - Display these metrics alongside data from other systems -{{< image filename="/images/rs/redis-enterprise-newrelic.png" >}} +![](/images/rs/redis-enterprise-newrelic.png) ## Install Redis' New Relic Integration for Redis Software The New Relic Integration for Redis is based on a feature of the Prometheus data source. Prometheus can forward metrics on to diff --git a/content/integrate/prometheus-with-redis-cloud/_index.md b/content/integrate/prometheus-with-redis-cloud/_index.md index 25870fb542..36d043369e 100644 --- a/content/integrate/prometheus-with-redis-cloud/_index.md +++ b/content/integrate/prometheus-with-redis-cloud/_index.md @@ -133,7 +133,7 @@ To get started with custom monitoring with Prometheus on Docker: 1. In your browser, sign in to Prometheus at `http://localhost:9090` to make sure the server is running. 1. Select **Status** and then **Targets** to check that Prometheus is collecting data from the Redis Cloud cluster. - {{The Redis Software target showing that Prometheus is connected to the Redis Software Cluster.}} + ![The Redis Software target showing that Prometheus is connected to the Redis Software Cluster.](/images/rs/prometheus-target.png) If Prometheus is connected to the cluster, you can type **node_up** in the Expression field on the Prometheus home page to see the cluster metrics. @@ -154,7 +154,7 @@ Once the Prometheus and Grafana Docker containers are running, and Prometheus is 1. Select **Prometheus** from the list of data source types. - {{The Prometheus data source in the list of data sources on Grafana.}} + ![The Prometheus data source in the list of data sources on Grafana.](/images/rs/prometheus-datasource.png) 1. Enter the Prometheus configuration information: @@ -162,7 +162,7 @@ Once the Prometheus and Grafana Docker containers are running, and Prometheus is - URL: `http://prometheus-server:9090` - Access: `Server` - {{The Prometheus connection form in Grafana.}} + ![The Prometheus connection form in Grafana.](/images/rc/prometheus-connection.png) > [!NOTE] > - If the network port is not accessible to the Grafana server, select the **Browser** option from the Access menu. diff --git a/content/integrate/railway-redis/_index.md b/content/integrate/railway-redis/_index.md index 1321e0f32b..1c0c10c470 100644 --- a/content/integrate/railway-redis/_index.md +++ b/content/integrate/railway-redis/_index.md @@ -16,7 +16,7 @@ weight: 7 [Railway](https://railway.com?utm_medium=integration&utm_source=docs&utm_campaign=redis) simplifies your infrastructure stack from databases to servers to observability with a single, scalable, easy-to-use platform. Companies of all sizes deploy full-stack applications on Railway and benefit from highly performant networking, intuitive vertical and horizontal scaling, and isolated environments with pull request deploys. Railway's template marketplace includes thousands of one-click deploy templates, including Redis. -{{< image filename="/images/rc/railway-redis-canvas.png" >}} +![](/images/rc/railway-redis-canvas.png) This is a guide to deploying Redis on Railway, using the official template. @@ -26,7 +26,7 @@ Navigate to a new Railway project at [railway.com/new](https://railway.com/new?u You can also deploy it via the [template](https://railway.com/deploy/redis) from the Railway template marketplace. -{{< image filename="/images/rc/railway-redis-add.gif" >}} +![](/images/rc/railway-redis-add.gif) Upon deployment, you will have a Redis service running in your project, deployed from the [redis](https://hub.docker.com/_/redis) Docker image. diff --git a/content/integrate/redis-data-integration/1.19.1/architecture/_index.md b/content/integrate/redis-data-integration/1.19.1/architecture/_index.md index 1113b45245..0f0a2b3ec7 100644 --- a/content/integrate/redis-data-integration/1.19.1/architecture/_index.md +++ b/content/integrate/redis-data-integration/1.19.1/architecture/_index.md @@ -57,7 +57,7 @@ outside the Redis Enterprise cluster where the target database is kept. However, RDI keeps its state and configuration data and also the change data streams in a Redis database on the same cluster as the target. The following diagram shows the pipeline steps and the path the data takes on its way from the source to the target: -{{< image filename="images/rdi/ingest/ingest-dataflow.webp" >}} +![](/images/rdi/ingest/ingest-dataflow.webp) When you first start RDI, the target database is empty and so all of the data in the source database is essentially "change" data. @@ -141,7 +141,7 @@ with the control plane. The diagram below shows all RDI components and the interactions between them: -{{< image filename="images/rdi/ingest/ingest-control-plane.webp" >}} +![](/images/rdi/ingest/ingest-control-plane.webp) ## Stream processor implementations @@ -170,7 +170,7 @@ The two operators running on both VMs use a leader election algorithm to decide VM is the active one (the "leader"). The diagram below shows this configuration: -{{< image filename="images/rdi/ingest/ingest-active-passive-vms.webp" >}} +![](/images/rdi/ingest/ingest-active-passive-vms.webp) See [Install on VMs](/content/integrate/redis-data-integration/1.19.1/installation/install-vm.md) for more information. diff --git a/content/integrate/redis-data-integration/1.19.1/data-pipelines/_index.md b/content/integrate/redis-data-integration/1.19.1/data-pipelines/_index.md index e926b1fba9..30ca993e8e 100644 --- a/content/integrate/redis-data-integration/1.19.1/data-pipelines/_index.md +++ b/content/integrate/redis-data-integration/1.19.1/data-pipelines/_index.md @@ -47,7 +47,7 @@ Data transformation involves two stages: The diagram below shows the flow of data through the pipeline: -{{< image filename="/images/rdi/ingest/RDIPipeDataflow.webp" >}} +![](/images/rdi/ingest/RDIPipeDataflow.webp) You can provide a job file for each source table that needs a custom transformation. You can also add a *default job file* for any tables that don't have their own. diff --git a/content/integrate/redis-data-integration/1.19.1/data-pipelines/data-denormalization.md b/content/integrate/redis-data-integration/1.19.1/data-pipelines/data-denormalization.md index 00b3b9b52c..8fa42654e4 100644 --- a/content/integrate/redis-data-integration/1.19.1/data-pipelines/data-denormalization.md +++ b/content/integrate/redis-data-integration/1.19.1/data-pipelines/data-denormalization.md @@ -127,7 +127,8 @@ You can also use custom keys for the parent entity, as long as you use the same To join one-to-many relationships, you can use the *Nesting* strategy. With this, the parent object (the "one") is represented as a JSON document with the children (the "many") nested inside it as a JSON map attribute. The diagram below shows a nesting with the child objects in a map called `InvoiceLineItems`: -{{< image filename="/images/rdi/ingest/nest-flow.webp" width="500px" >}} +![](/images/rdi/ingest/nest-flow.webp) +{width="500px"} To configure normalization, you must first configure the parent entity to use JSON as the target data type. Add `data_type: json` to the parent job as shown in the example below: diff --git a/content/integrate/redis-data-integration/1.19.1/data-pipelines/prepare-dbs/oracle.md b/content/integrate/redis-data-integration/1.19.1/data-pipelines/prepare-dbs/oracle.md index 086a9690fb..dd3105ef32 100644 --- a/content/integrate/redis-data-integration/1.19.1/data-pipelines/prepare-dbs/oracle.md +++ b/content/integrate/redis-data-integration/1.19.1/data-pipelines/prepare-dbs/oracle.md @@ -1178,7 +1178,7 @@ After you run an initial [snapshot](/content/integrate/redis-data-integration/1.19.1/data-pipelines/_index.md#pipeline-lifecycle), the XML data appears in your Redis target database: -{{< image filename="/images/rdi/ingest/xmltype-example.webp" >}} +![](/images/rdi/ingest/xmltype-example.webp) ## FAQ diff --git a/content/integrate/redis-data-integration/1.19.1/quick-start-guide.md b/content/integrate/redis-data-integration/1.19.1/quick-start-guide.md index 8ba257c77d..f774e3c023 100644 --- a/content/integrate/redis-data-integration/1.19.1/quick-start-guide.md +++ b/content/integrate/redis-data-integration/1.19.1/quick-start-guide.md @@ -25,7 +25,7 @@ In this tutorial you will learn how to install RDI and set up a pipeline to inge The following diagram shows the structure of the pipeline we will create (see the [architecture overview](/content/integrate/redis-data-integration/1.19.1/architecture/_index.md#overview) to learn how the pipeline works): -{{< image filename="images/rdi/ingest/ingest-qsg.webp" >}} +![](/images/rdi/ingest/ingest-qsg.webp) Here, the RDI *collector* tracks changes in PostgreSQL and writes them to streams in the RDI database in Redis. The *stream processor* then reads data records from the RDI diff --git a/content/integrate/redis-data-integration/architecture/_index.md b/content/integrate/redis-data-integration/architecture/_index.md index 3d9fb45d2e..c55e9db9f5 100644 --- a/content/integrate/redis-data-integration/architecture/_index.md +++ b/content/integrate/redis-data-integration/architecture/_index.md @@ -57,7 +57,7 @@ outside the Redis Enterprise cluster where the target database is kept. However, RDI keeps its state and configuration data and also the change data streams in a Redis database on the same cluster as the target. The following diagram shows the pipeline steps and the path the data takes on its way from the source to the target: -{{< image filename="images/rdi/ingest/ingest-dataflow.webp" >}} +![](/images/rdi/ingest/ingest-dataflow.webp) When you first start RDI, the target database is empty and so all of the data in the source databases is essentially "change" data. @@ -141,7 +141,7 @@ with the control plane. The diagram below shows all RDI components and the interactions between them: -{{< image filename="images/rdi/ingest/ingest-control-plane.webp" >}} +![](/images/rdi/ingest/ingest-control-plane.webp) ## Stream processor implementations @@ -170,7 +170,7 @@ The two operators running on both VMs use a leader election algorithm to decide VM is the active one (the "leader"). The diagram below shows this configuration: -{{< image filename="images/rdi/ingest/ingest-active-passive-vms.webp" >}} +![](/images/rdi/ingest/ingest-active-passive-vms.webp) See [Install on VMs](/content/integrate/redis-data-integration/installation/install-vm.md) for more information. diff --git a/content/integrate/redis-data-integration/data-pipelines/_index.md b/content/integrate/redis-data-integration/data-pipelines/_index.md index 37a4bdd7ef..f862651ce1 100644 --- a/content/integrate/redis-data-integration/data-pipelines/_index.md +++ b/content/integrate/redis-data-integration/data-pipelines/_index.md @@ -49,7 +49,7 @@ Data transformation involves two stages: The diagram below shows the flow of data through the pipeline: -{{< image filename="/images/rdi/ingest/RDIPipeDataflow.webp" >}} +![](/images/rdi/ingest/RDIPipeDataflow.webp) You can provide a job file for each source table that needs a custom transformation. You can also add a *default job file* for any tables that don't have their own. diff --git a/content/integrate/redis-data-integration/data-pipelines/data-denormalization.md b/content/integrate/redis-data-integration/data-pipelines/data-denormalization.md index 9e45b7c81d..6cacf08712 100644 --- a/content/integrate/redis-data-integration/data-pipelines/data-denormalization.md +++ b/content/integrate/redis-data-integration/data-pipelines/data-denormalization.md @@ -129,7 +129,8 @@ You can also use custom keys for the parent entity, as long as you use the same To join one-to-many relationships, you can use the *Nesting* strategy. With this, the parent object (the "one") is represented as a JSON document with the children (the "many") nested inside it as a JSON map attribute. The diagram below shows a nesting with the child objects in a map called `InvoiceLineItems`: -{{< image filename="/images/rdi/ingest/nest-flow.webp" width="500px" >}} +![](/images/rdi/ingest/nest-flow.webp) +{width="500px"} To configure normalization, you must first configure the parent entity to use JSON as the target data type. Add `data_type: json` to the parent job as shown in the example below: diff --git a/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md b/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md index e555f755d5..e9e7f25a36 100644 --- a/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md +++ b/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md @@ -1181,7 +1181,7 @@ After you run an initial [snapshot](/content/integrate/redis-data-integration/data-pipelines/_index.md#pipeline-lifecycle), the XML data appears in your Redis target database: -{{< image filename="/images/rdi/ingest/xmltype-example.webp" >}} +![](/images/rdi/ingest/xmltype-example.webp) ## FAQ diff --git a/content/integrate/redis-data-integration/quick-start-guide.md b/content/integrate/redis-data-integration/quick-start-guide.md index 81e4b59d67..68ea3c49ac 100644 --- a/content/integrate/redis-data-integration/quick-start-guide.md +++ b/content/integrate/redis-data-integration/quick-start-guide.md @@ -25,7 +25,7 @@ In this tutorial you will learn how to install RDI and set up a pipeline to inge The following diagram shows the structure of the pipeline we will create (see the [architecture overview](/content/integrate/redis-data-integration/architecture/_index.md#overview) to learn how the pipeline works): -{{< image filename="images/rdi/ingest/ingest-qsg.webp" >}} +![](/images/rdi/ingest/ingest-qsg.webp) Here, the RDI *collector* tracks changes in PostgreSQL and writes them to streams in the RDI database in Redis. The *stream processor* then reads data records from the RDI diff --git a/content/integrate/uptrace-with-redis-enterprise/_index.md b/content/integrate/uptrace-with-redis-enterprise/_index.md index d0f0ed8f25..f92fe24fff 100644 --- a/content/integrate/uptrace-with-redis-enterprise/_index.md +++ b/content/integrate/uptrace-with-redis-enterprise/_index.md @@ -30,7 +30,7 @@ You can use Uptrace to: - Set up automatic alerts and receive notifications via email, Slack, Telegram, and others. - Monitor your app performance and logs using [OpenTelemetry tracing](https://uptrace.dev/opentelemetry/distributed-tracing.html). -{{< image filename="/images/rs/uptrace-redis-nodes.png" >}} +![](/images/rs/uptrace-redis-nodes.png) ## Install Collector and Uptrace diff --git a/content/integrate/write-behind/data-transformation/_index.md b/content/integrate/write-behind/data-transformation/_index.md index 310d07bc70..c456241957 100644 --- a/content/integrate/write-behind/data-transformation/_index.md +++ b/content/integrate/write-behind/data-transformation/_index.md @@ -30,7 +30,7 @@ There are two types of data transformations in Write-behind: 1. If the user wants to add or modify this default mapping, Write-behind provides declarative data transformations. These transformations are represented in YAML files. Each file contains a job, which is a set of transformations per source table. See [declarative transformations](/content/integrate/write-behind/data-transformation/data-transformation-pipeline.md) for more information. -{{< image filename="/images/rdi/data-transformation-flow.png" >}} +![](/images/rdi/data-transformation-flow.png) ## More info diff --git a/content/integrate/write-behind/data-transformation/data-transformation-pipeline.md b/content/integrate/write-behind/data-transformation/data-transformation-pipeline.md index 6f28389737..17d689f7b1 100644 --- a/content/integrate/write-behind/data-transformation/data-transformation-pipeline.md +++ b/content/integrate/write-behind/data-transformation/data-transformation-pipeline.md @@ -25,7 +25,7 @@ The ingested format and types are different from one source to another. Currentl Each job describes the transformation logic to perform on data from a single source. The source is typically a database table or collection and is specified as the full name of this table/collection. The job may include filtering logic to skip data that matches a condition. Other logical steps in the job will transform the data into the desired output that will be stored in Redis as hashes or JSON. -{{< image filename="/images/rdi/data-transformation-pipeline.png" >}} +![](/images/rdi/data-transformation-pipeline.png) ## Default job In situations where there is a need to perform a transformation on all ingested records without creating a specific job for specific tables, the default job is used. The transformation associated with this job will be applied to all tables that lack their own explicitly defined jobs. The default job must have a table name of "*", and only one instance of this type of job is permitted. diff --git a/content/integrate/write-behind/monitoring-guide.md b/content/integrate/write-behind/monitoring-guide.md index f6cc9849fb..cc3240d52f 100644 --- a/content/integrate/write-behind/monitoring-guide.md +++ b/content/integrate/write-behind/monitoring-guide.md @@ -36,7 +36,7 @@ Write-behind allows collecting and exporting its metrics to [Prometheus](https:/ [`redis-di monitor`](/content/integrate/write-behind/reference/cli/redis-di-monitor.md) command. The diagram describes this flow and the components involved: -{{< image filename="/images/rdi/monitoring-diagram.png" >}} +![](/images/rdi/monitoring-diagram.png) > Note: The host names and ports above are examples only and can be changed as needed. @@ -97,15 +97,15 @@ Optionally, you may deploy the sample Grafana dashboard to monitor the status of 1. Log into Grafana and navigate to the list of dashboards, then choose **New > Import**: -{{< image filename="/images/rdi/monitoring-grafana-new-dash.png" >}} +![](/images/rdi/monitoring-grafana-new-dash.png) 1. On the next screen, select **Upload JSON file** and upload the file you downloaded in step 1. Make sure you select the data source that is connected to the Write-behind metrics exporter: -{{< image filename="/images/rdi/monitoring-grafana-dash-configure.png" >}} +![](/images/rdi/monitoring-grafana-dash-configure.png) 1. Select **Import** and make sure you choose the jobs to monitor from the drop-down list (this will be empty if you don't have any jobs running yet): -{{< image filename="/images/rdi/monitoring-grafana-dash-running.png" >}} +![](/images/rdi/monitoring-grafana-dash-running.png) ## Write-behind metrics diff --git a/content/integrate/write-behind/quickstart/write-behind-guide.md b/content/integrate/write-behind/quickstart/write-behind-guide.md index d45161ab72..ffc07bb354 100644 --- a/content/integrate/write-behind/quickstart/write-behind-guide.md +++ b/content/integrate/write-behind/quickstart/write-behind-guide.md @@ -33,7 +33,7 @@ The **target** data store to which the write-behind pipeline connects and writes The write-behind pipeline is composed of one or more **jobs**. Each job is responsible for capturing change for one key pattern in Redis and mapping it to one or more tables in the downstream data store. Each job is defined in a YAML file. -{{< image filename="/images/rdi/redis-di-write-behind.png" >}} +![](/images/rdi/redis-di-write-behind.png) ## Supported data stores