diff --git a/content/embeds/cluster-setup.md b/content/embeds/cluster-setup.md index c02410df0f..dec2bb5733 100644 --- a/content/embeds/cluster-setup.md +++ b/content/embeds/cluster-setup.md @@ -6,21 +6,21 @@ 1. Select **Create new cluster**. - {{When you first install Redis Software, you need to set up a cluster.}} + ![When you first install Redis Software, you need to set up a cluster.](/images/rs/screenshots/cluster/setup/create-cluster.png) 2. Enter an email and password for the administrator account, then select **Next** to proceed to cluster setup. - {{Set the credentials for your admin user.}} + ![Set the credentials for your admin user.](/images/rs/screenshots/cluster/setup/admin-credentials.png) You can also use these credentials to connect to the [REST API]({{< relref "/operate/rs/references/rest-api" >}}). 3. Enter your cluster license key if you have one. Otherwise, a trial version is installed. - {{Enter your cluster license key if you have one.}} + ![Enter your cluster license key if you have one.](/images/rs/screenshots/cluster/setup/cluster-license-key.png) 4. In the **Configuration** section, enter a cluster FQDN such as `cluster.local`, then select **Next**. - {{Configure the cluster FQDN.}} + ![Configure the cluster FQDN.](/images/rs/screenshots/cluster/setup/config-cluster.png) {{< warning >}} If the FQDN is `cluster.local`, you cannot configure DNS. You cannot change the FQDN after cluster creation. @@ -28,8 +28,8 @@ If the FQDN is `cluster.local`, you cannot configure DNS. You cannot change the 1. On the node setup screen, select **Create cluster** to accept the defaults. - {{Configure the node specific settings.}} + ![Configure the node specific settings.](/images/rs/screenshots/cluster/setup/node-settings.png) 6. Select **OK** to acknowledge the replacement of the HTTPS TLS certificate on the node. If you receive a browser warning, you can proceed safely. - {{Modal shown when a page refresh is needed because the certificates have been updated.}} + ![Modal shown when a page refresh is needed because the certificates have been updated.](/images/rs/screenshots/cluster/setup/https-page-refresh-modal.png) diff --git a/content/embeds/quick-db-setup.md b/content/embeds/quick-db-setup.md index 4347841262..29201787c0 100644 --- a/content/embeds/quick-db-setup.md +++ b/content/embeds/quick-db-setup.md @@ -1,18 +1,19 @@ 1. On the **Databases** screen, select **Quick database**. - {{Select Quick database on the Databases screen.}} + ![Select Quick database on the Databases screen.](/images/rs/screenshots/databases/db-screen.png) 1. Enter 12000 for the **Port**. If port 12000 is not available, enter any available port number between 10000 to 19999 or leave it blank to let the cluster assign a port number for you. You will use this port number to connect to the database. - {{Create a quick database.}} + ![Create a quick database.](/images/rs/screenshots/databases/quick-db.png) 1. Select **Create** to create your database. When you see **Database active** appear on the database configuration screen, the database is activated and ready for you to use. -{{Database active icon.}} +![Database active icon.](/images/rs/icons/db-active-icon.png) +{width="150px"} You now have a Redis database! \ No newline at end of file diff --git a/content/embeds/rc-aa-cidr.md b/content/embeds/rc-aa-cidr.md index 5d1cd96743..1a9e9faa80 100644 --- a/content/embeds/rc-aa-cidr.md +++ b/content/embeds/rc-aa-cidr.md @@ -2,8 +2,10 @@ Every CIDR should be unique to properly route network traffic between each Activ When all **Deployment CIDR** regions display a green checkmark, you're ready to continue. -{{Green checkmarks indicate valid CIDR address values.}} +![Green checkmarks indicate valid CIDR address values.](/images/rc/icon-cidr-address-ok.png) +{width="30px"} Red exclamation marks indicate error conditions; the tooltip provides additional details. -{{Red exclamation points indicate CIDR address problems.}} \ No newline at end of file +![Red exclamation points indicate CIDR address problems.](/images/rc/icon-cidr-address-error.png) +{width="30px"} \ No newline at end of file diff --git a/content/embeds/rc-cost-report-csv.md b/content/embeds/rc-cost-report-csv.md index 11189fa7d5..8a821e1a1d 100644 --- a/content/embeds/rc-cost-report-csv.md +++ b/content/embeds/rc-cost-report-csv.md @@ -3,6 +3,7 @@ --- Select the **Cost report** button to download a report of all shard costs in CSV format. -{{The cost report download button.}} +![The cost report download button.](/images/rc/button-cost-report-download.png) +{width="150px"} The report gives a breakdown of all your Redis billing unit costs, per subscription and database, by month. Subscriptions under the minimum subscription price are broken down into actual billing unit prices and the difference from minimum price. \ No newline at end of file diff --git a/content/embeds/rc-create-db-first-steps.md b/content/embeds/rc-create-db-first-steps.md index afba75ac13..9b6420a8e3 100644 --- a/content/embeds/rc-create-db-first-steps.md +++ b/content/embeds/rc-create-db-first-steps.md @@ -6,6 +6,7 @@ To create a database in your Redis Cloud account: 2. Select the **New database** button. - {{The New Database button creates a new database.}} + ![The New Database button creates a new database.](/images/rc/button-database-new.png) + {width="120px"} This displays the **Create database** screen. \ No newline at end of file diff --git a/content/embeds/rc-create-db-use-cases.md b/content/embeds/rc-create-db-use-cases.md index 9018ffbf8d..78c39eb8b1 100644 --- a/content/embeds/rc-create-db-use-cases.md +++ b/content/embeds/rc-create-db-use-cases.md @@ -1,6 +1,6 @@ 3. Select your Redis use case. There are four pre-defined use cases: - {{The Redis Use case panel}} + ![The Redis Use case panel](/images/rc/create-database-redis-use-cases.png) - **Cache**: Stores short-term or volatile data. Can be used for session management, semantic cache, session store, and other uses where data is short-lived. - **Database**: Stores durable and consistent data. Can be used for document databases, feature storage, gaming leaderboards, durable caches, and other uses where your data needs to be highly available and persistent. diff --git a/content/embeds/rc-credit-card-add.md b/content/embeds/rc-credit-card-add.md index fb4bff7a6f..bdec5708b0 100644 --- a/content/embeds/rc-credit-card-add.md +++ b/content/embeds/rc-credit-card-add.md @@ -1,9 +1,11 @@ If you have not already added a business address to your account, you must enter one. Redis uses your business address for communication, invoicing, and tax purposes. -{{The Add credit card screen before a business address has already been added.}} +![The Add credit card screen before a business address has already been added.](/images/rc/billing-add-first-card.png) +{width="80%"} If you already have a business address, you don't need to enter one here. See [Account settings]({{< relref "/operate/rc/accounts/account-settings" >}}) to learn how to update your business address. -{{The Add credit card screen after a business address has already been added.}} +![The Add credit card screen after a business address has already been added.](/images/rc/billing-add-credit-card.png) +{width="80%"} If the card's billing address is the same as your account's business address, select **Same as business address** to fill the billing address with your business address details. \ No newline at end of file diff --git a/content/embeds/rc-endpoint-description.md b/content/embeds/rc-endpoint-description.md index af5cc2b452..7cd6a0d71b 100644 --- a/content/embeds/rc-endpoint-description.md +++ b/content/embeds/rc-endpoint-description.md @@ -12,4 +12,4 @@ horse-battery-staple-12345.db.redis.io You can see the Dynamic endpoints for databases with both static and dynamic endpoints by expanding the **Dynamic endpoints** section in the **General** section of the **Configuration** tab. -{{The Static and dynamic endpoints for a database with both kinds of endpoints.}} \ No newline at end of file +![The Static and dynamic endpoints for a database with both kinds of endpoints.](/images/rc/databases-configuration-general-endpoints-legacy.png) \ No newline at end of file diff --git a/content/embeds/rc-get-prometheus-endpoint.md b/content/embeds/rc-get-prometheus-endpoint.md index 22b3b5c406..69d7700a83 100644 --- a/content/embeds/rc-get-prometheus-endpoint.md +++ b/content/embeds/rc-get-prometheus-endpoint.md @@ -1,5 +1,6 @@ In the **Metrics** tab of your database, select **Connect to Prometheus > Copy Prometheus endpoint** to save your Prometheus endpoint to the clipboard. -{{Use the Connect to Prometheus button to get the Prometheus endpoint.}} +![Use the Connect to Prometheus button to get the Prometheus endpoint.](/images/rc/database-metrics-connect-prometheus.png) +{width="250px"} You can also get the Prometheus endpoint by calling [`GET /subscriptions/{subscriptionId}`]({{< relref "/operate/rc/api/api-reference#tag/Subscriptions-Pro/operation/getSubscriptionById" >}}) and getting the `prometheusEndpoint` from the response. diff --git a/content/embeds/rc-marketplace-account-add.md b/content/embeds/rc-marketplace-account-add.md index 8c2ed21a7d..a959b7bcbb 100644 --- a/content/embeds/rc-marketplace-account-add.md +++ b/content/embeds/rc-marketplace-account-add.md @@ -6,12 +6,14 @@ To do this: 1. Select **Add Marketplace account**. - {{The Add marketplace account button.}} + ![The Add marketplace account button.](/images/rc/add-marketplace-account.png) + {width="300px"} 1. Select the marketplace account you want to connect and confirm that it will pay for your Redis Cloud resources going forward. 1. Select **Connect account**. - {{The Connect account button.}} + ![The Connect account button.](/images/rc/button-connect-account.png) + {width="150px"} Your marketplace account is now connected to your Redis Cloud account. If you would like to disconnect your marketplace account from your Redis Cloud account, select **Disconnect**. \ No newline at end of file diff --git a/content/embeds/rc-opt-in-to-72.md b/content/embeds/rc-opt-in-to-72.md index 9a141ea491..475cad43ee 100644 --- a/content/embeds/rc-opt-in-to-72.md +++ b/content/embeds/rc-opt-in-to-72.md @@ -1,6 +1,7 @@ Select **Opt-in to 7.2** to request to upgrade your subscription and databases to Redis 7.2 (*Redis 6.2 and earlier only*). -{{Opt-in to 7.2 button.}} +![Opt-in to 7.2 button.](/images/rc/button-opt-in-to-72.png) +{width="150px"} The upgrade will start one week from your request, according to [maintenance windows]({{< relref "/operate/rc/subscriptions/maintenance/set-maintenance-windows" >}}). diff --git a/content/embeds/rc-rdi-create-rdi-workspace.md b/content/embeds/rc-rdi-create-rdi-workspace.md index adb94a13aa..ca1403ea01 100644 --- a/content/embeds/rc-rdi-create-rdi-workspace.md +++ b/content/embeds/rc-rdi-create-rdi-workspace.md @@ -2,19 +2,23 @@ To create a Data Integration workspace for an existing [Pro subscription]({{< re 1. From the Redis Cloud console, select **Data Integration** from the left-hand menu. If you don't have any workspaces yet, select **Create workspace** to go to the **Create workspace** page. - {{The create workspace button.}} + ![The create workspace button.](/images/rc/rdi/rdi-create-workspace-button.png) + {width="200px"} If you already have a workspace deployed, you'll see your current workspaces. Select **New workspace** to go to the **Create workspace** page. - {{The new workspace button.}} + ![The new workspace button.](/images/rc/rdi/rdi-new-workspace-button.png) + {width="150px"} You can also go to the **Data Integration** tab from your subscription or database page and select **Create workspace** to go to the **Create workspace** page for your subscription. - {{The create workspace button.}} + ![The create workspace button.](/images/rc/rdi/rdi-create-workspace-button.png) + {width="200px"} 2. Select your Pro subscription from the list if it's not already selected. - {{The select pro subscription drop down.}} + ![The select pro subscription drop down.](/images/rc/rdi/rdi-create-workspace-select-subscription.png) + {width="80%"} 3. A **Data Integration subnet (CIDR)** is automatically generated for you. Each RDI workspace uses a dedicated `/22` CIDR. @@ -27,10 +31,12 @@ To create a Data Integration workspace for an existing [Pro subscription]({{< re If the automatic suggestion is missing or unsuitable, select another unused `/22` CIDR in the same private range. For more information, see [VPC CIDR block association restrictions](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-cidr-blocks.html#vpc-resize). - {{The select pro subscription drop down.}} + ![The select pro subscription drop down.](/images/rc/rdi/rdi-create-workspace-cidr.png) + {width="80%"} 4. Select **Create workspace** to create your workspace. - {{The create workspace button.}} + ![The create workspace button.](/images/rc/rdi/rdi-create-workspace-button.png) + {width="200px"} Your workspace will be created in the background. You can select **Create pipeline** to [create your pipeline]({{}}) while the workspace is provisioning, or you can select **Create pipeline later** to go back to the Redis Cloud console. diff --git a/content/embeds/rc-tags-tag-module.md b/content/embeds/rc-tags-tag-module.md index d09e5690e5..0d7b7e5f5d 100644 --- a/content/embeds/rc-tags-tag-module.md +++ b/content/embeds/rc-tags-tag-module.md @@ -1,6 +1,6 @@ You can select the tag's **Key** and **Value** from the suggestions, or you can enter your own. -{{The New tag fields.}} +![The New tag fields.](/images/rc/tags-new-tag.png) A valid tag must follow these guidelines: - Tag keys must be between 1 and 64 characters long, and values must be at least 1 character long. @@ -12,8 +12,10 @@ After you add your first tag, you can: - Select **Delete** next to a tag to delete it. - {{Delete button.}} + ![Delete button.](/images/rc/icon-delete-lb.png) + {width="36px"} - Select **Add additional tag** to add another tag. - {{The Add additional tag button.}} \ No newline at end of file + ![The Add additional tag button.](/images/rc/tags-button-add-additional-tag.png) + {width="200px"} \ No newline at end of file diff --git a/content/embeds/rc-version-upgrade.md b/content/embeds/rc-version-upgrade.md index 2871f8294a..a598d588ea 100644 --- a/content/embeds/rc-version-upgrade.md +++ b/content/embeds/rc-version-upgrade.md @@ -1,10 +1,12 @@ Select **Version upgrade** to request to upgrade your subscription and databases if there is a later version available. -{{Version upgrade button.}} +![Version upgrade button.](/images/rc/button-version-upgrade.png) +{width="150px"} Select the version to upgrade your databases from the list and select **Upgrade** to submit the upgrade request. -{{Version upgrade request list with version 7.4 selected.}} +![Version upgrade request list with version 7.4 selected.](/images/rc/version-upgrade-request.png) +{width="80%"} The upgrade will start one week from your request, according to your subscription's [maintenance windows]({{< relref "/operate/rc/subscriptions/maintenance/set-maintenance-windows" >}}). diff --git a/content/embeds/rdi-db-reqs.md b/content/embeds/rdi-db-reqs.md index e41e39316b..9c10a728bd 100644 --- a/content/embeds/rdi-db-reqs.md +++ b/content/embeds/rdi-db-reqs.md @@ -43,13 +43,13 @@ When you create the RDI database, expand the **Clustering** section and make sure the **Sharding** option is *unchecked* (as shown below). - {{< image filename="images/rdi/ingest/RDIClusterSetting.webp" alt="The Sharding option is unchecked in the Clustering section of the create database form." >}} + ![The Sharding option is unchecked in the Clustering section of the create database form.](/images/rdi/ingest/RDIClusterSetting.webp) You can check if your RDI database is clustered from its **Configuration** tab in the Cluster Manager UI. In the **Clustering** section, **Sharding** should be set to **Disabled**, as shown in the following screenshot: - {{< image filename="images/rdi/ingest/RDICheckUnclustered.webp" alt="The Clustering section of the database Configuration tab shows Sharding: Disabled." >}} + ![The Clustering section of the database Configuration tab shows Sharding: Disabled.](/images/rdi/ingest/RDICheckUnclustered.webp) If you find the database has been clustered by mistake, you must create a new database with sharding disabled before continuing with the RDI installation. diff --git a/content/embeds/replica-of-tls-config.md b/content/embeds/replica-of-tls-config.md index 10b30e6df4..77f4f22da2 100644 --- a/content/embeds/replica-of-tls-config.md +++ b/content/embeds/replica-of-tls-config.md @@ -6,7 +6,7 @@ To enable TLS for Replica Of cluster connections: 1. Expand the **Replica Of and Active-Active authentication (Syncer certificate)** section. - {{Syncer certificate for Replica Of and Active-Active authentication.}} + ![Syncer certificate for Replica Of and Active-Active authentication.](/images/rs/screenshots/cluster/security-syncer-cert.png) 1. Download or copy the syncer certificate. @@ -18,7 +18,7 @@ To enable TLS for Replica Of cluster connections: 1. Select **Mutual TLS (Client authentication)**. - {{Replica Of TLS authentication configuration.}} + ![Replica Of TLS authentication configuration.](/images/rs/screenshots/databases/security-tls-replica-of.png) 1. Select **+ Add certificate**, paste or upload the syncer certificate, then select **Done**. diff --git a/content/embeds/rs-observability.md b/content/embeds/rs-observability.md index caa1b26859..65e7a09c93 100644 --- a/content/embeds/rs-observability.md +++ b/content/embeds/rs-observability.md @@ -565,7 +565,7 @@ The built-in configuration, `error_rules.yml`, has a single alert: Critical Conn If you open the Prometheus console, by default located at port 9090, and select the Alert tab, you will see this alert, as well as the alerts in any other file you have included as a rules file. -{{< image filename="/images/playbook_prometheus-alerts.png" alt="prometheus alerts image" >}} +![prometheus alerts image](/images/playbook_prometheus-alerts.png) The following is a list of alerts contained in the `alerts.yml` file. There are several points to consider: diff --git a/content/embeds/rs-prometheus-grafana-quickstart.md b/content/embeds/rs-prometheus-grafana-quickstart.md index 1e7483719a..3bfc0911ed 100644 --- a/content/embeds/rs-prometheus-grafana-quickstart.md +++ b/content/embeds/rs-prometheus-grafana-quickstart.md @@ -14,7 +14,8 @@ You can use Prometheus and Grafana to: - Display Redis Software metrics alongside data from other systems -{{Graphic showing how Prometheus and Grafana collect and display data from a Redis Software Cluster. Prometheus collects metrics from the Redis Software cluster, and Grafana queries those metrics for visualization.}} +![Graphic showing how Prometheus and Grafana collect and display data from a Redis Software Cluster. Prometheus collects metrics from the Redis Software cluster, and Grafana queries those metrics for visualization.](/images/rs/grafana-prometheus.png) +{width="80%" class="mx-auto block my-6 p-4 border border-redis-pen-300 rounded-lg shadow-sm"} To get started with Prometheus and Grafana, see the following [quick start](#quick-start) or see [Redis Software Observability with Prometheus and Grafana](https://redis.io/learn/operate/observability/redis-software-prometheus-and-grafana) for a more detailed tutorial. @@ -197,7 +198,7 @@ We recommend running Prometheus in Docker only for development and testing. 1. Select **Status** and then **Targets** to check that Prometheus is collecting data from your Redis Software 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. @@ -216,14 +217,14 @@ We recommend running Prometheus in Docker only for development and testing. 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: - Name: `redis-enterprise` - URL: `http://:9090` - {{The Prometheus connection form in Grafana.}} + ![The Prometheus connection form in Grafana.](/images/rs/prometheus-connection.png) {{< note >}} diff --git a/content/embeds/rs-quick-db-setup-7-8.md b/content/embeds/rs-quick-db-setup-7-8.md index ee2e984599..7cb67f5550 100644 --- a/content/embeds/rs-quick-db-setup-7-8.md +++ b/content/embeds/rs-quick-db-setup-7-8.md @@ -1,18 +1,19 @@ 1. On the **Databases** screen, select **Quick database**. - {{Select Quick database on the Databases screen.}} + ![Select Quick database on the Databases screen.](/images/rs/screenshots/databases/db-screen.png) 1. Enter 12000 for the **Port**. If port 12000 is not available, enter any available port number between 10000 to 19999 or leave it blank to let the cluster assign a port number for you. You will use this port number to connect to the database. - {{Create a quick database.}} + ![Create a quick database.](/images/rs/screenshots/databases/quick-db-7-8-2.png) 1. Select **Create** to create your database. When you see **Database active** appear on the database configuration screen, the database is activated and ready for you to use. -{{Database active icon.}} +![Database active icon.](/images/rs/icons/db-active-icon.png) +{width="150px"} You now have a Redis database! \ No newline at end of file diff --git a/content/embeds/tls-configuration-procedure.md b/content/embeds/tls-configuration-procedure.md index 8f96f2b593..2763a48c7f 100644 --- a/content/embeds/tls-configuration-procedure.md +++ b/content/embeds/tls-configuration-procedure.md @@ -10,7 +10,7 @@ To enable TLS for Replica Of communication only on the source database: 1. Enable **TLS**. - {{< image filename="/images/rs/database-tls-config.png" alt="Database TLS Configuration" >}} + ![Database TLS Configuration](/images/rs/database-tls-config.png) 1. Select the communication that you want to secure: @@ -34,7 +34,7 @@ To enable TLS for Replica Of communication only on the source database: 1. Select the **Add** button to open the certificate dialog. {{< image filename="/images/rs/icon_add.png#no-click" alt="Add button" >}} - {{< image filename="/images/rs/database-tls-replica-certs.png" alt="Database TLS Configuration" >}} + ![Database TLS Configuration](/images/rs/database-tls-replica-certs.png) 1. Enter the copied certificate text into the text box below the **Enforce client authentication** checkbox. @@ -58,7 +58,7 @@ To enable TLS for Replica Of and client communication on the source database: 1. Enable **TLS** and select **Require TLS for all communications**. - {{< image filename="/images/rs/database-tls-all.png" alt="database-tls-all" >}} + ![database-tls-all](/images/rs/database-tls-all.png) By default, client authentication is enforced so you must enter the syncer certificates of the clusters that host the destination databases. @@ -78,7 +78,7 @@ To enable TLS for Replica Of and client communication on the source database: 1. Use the **Add** button to open the certificate dialog. {{< image filename="/images/rs/icon_add.png#no-click" alt="Add button" >}} - {{< image filename="/images/rs/database-tls-replica-certs.png" alt="Database TLS Configuration" >}} + ![Database TLS Configuration](/images/rs/database-tls-replica-certs.png) 1. Enter the copied certificate text into the text box below the **Enforce client authentication** checkbox. 1. Use the **Save** button to save your changes. diff --git a/content/operate/oss_and_stack/stack-with-enterprise/bloom/_index.md b/content/operate/oss_and_stack/stack-with-enterprise/bloom/_index.md index cdbd8936f2..6d0e3e714e 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/bloom/_index.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/bloom/_index.md @@ -48,7 +48,7 @@ set to 1. This looks fairly similar to how buckets in a hash table are mapped. To check if an item is present or not, the hash is computed and the filter sees if the corresponding bit is set or not. -{{< image filename="/images/rs/rebloom-hash1.png" >}} +![](/images/rs/rebloom-hash1.png) Of course, this is subject to collisions. If a collision happens, the filter returns a false positive - indicating that the entry is @@ -68,7 +68,7 @@ The actual value of *bpe* is determined at the time the filter is created. Generally the more bits per element, the lower the likelihood of false positives. -{{< image filename="/images/rs/rebloom-hash3.png" >}} +![](/images/rs/rebloom-hash3.png) In the example above, all three bits would need to be set in order for the filter to return a positive result. diff --git a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/gears-v1/jvm/install.md b/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/gears-v1/jvm/install.md index 8974904cfb..d27f7f497c 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/gears-v1/jvm/install.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/gears-v1/jvm/install.md @@ -31,7 +31,8 @@ Before you can use RedisGears with the JVM, you need to install the RedisGears m 1. From the Redis Software admin console's **databases** page, select the **Add** button to create a new database: - {{The Add icon}} + ![The Add icon](/images/rs/icon_add.png) + {width="30px"} 1. Confirm that you want to create a new Redis database with the **Next** button. @@ -41,7 +42,8 @@ Before you can use RedisGears with the JVM, you need to install the RedisGears m 1. Select **Add Configuration**, enter `Plugin gears_jvm` in the box, then select the **OK** button: - {{The Save icon}} + ![The Save icon](/images/rs/icon_save.png) + {width="30px"} > [!NOTE] > You can configure additional JVM options in this box. For example:

diff --git a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/gears-v1/python/install.md b/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/gears-v1/python/install.md index f30b40f366..a90f6a8b61 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/gears-v1/python/install.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/gears-v1/python/install.md @@ -31,7 +31,8 @@ Before you can use RedisGears with Python, you need to install the RedisGears mo 1. From the Redis Software admin console's **databases** page, select the **Add** button to create a new database: - {{The Add icon}} + ![The Add icon](/images/rs/icon_add.png) + {width="30px"} 1. Confirm that you want to create a new Redis database with the **Next** button. @@ -41,7 +42,8 @@ Before you can use RedisGears with Python, you need to install the RedisGears mo 1. Select **Add Configuration**, enter `Plugin gears_python CreateVenv 1` in the box, then select the **OK** button: - {{The Save icon}} + ![The Save icon](/images/rs/icon_save.png) + {width="30px"} > [!NOTE] > Only RedisGears v1.2 and later require this configuration. diff --git a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/graph/graph-quickstart.md b/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/graph/graph-quickstart.md index ba0b7e352e..b88a8e7abf 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/graph/graph-quickstart.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/graph/graph-quickstart.md @@ -233,7 +233,7 @@ You can use the [Redis Insight](/content/develop/tools/insight/_index.md) workbe After you run a query, the output log displays a visual representation of your graph's nodes and relationships: -{{Visualize a graph with Redis Insight workbench.}} +![Visualize a graph with Redis Insight workbench.](/images/modules/visualize-graph.png) ## More info diff --git a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/Quick_Start_RI.md b/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/Quick_Start_RI.md index 65d5135cd8..7d3a586c4a 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/Quick_Start_RI.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/Quick_Start_RI.md @@ -25,35 +25,35 @@ If you haven't already installed Redis Insight, you can download the latest vers Open the Redis Insight application, and connect to your database by clicking on its database alias. -{{< image filename="/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-0.png" >}} +![](/images/triggers-and-functions/tf-rdi-0.png) ## Load a library Click on the triggers and functions icon and then on **+ Library** as shown below. -{{< image filename="/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-1.png" >}} +![](/images/triggers-and-functions/tf-rdi-1.png) Add your code to the **Library Code** section of the right-hand panel and then click **Add Library**. -{{< image filename="/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-2.png" >}} +![](/images/triggers-and-functions/tf-rdi-2.png) You'll see the following when the library was added: -{{< image filename="/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-3.png" >}} +![](/images/triggers-and-functions/tf-rdi-3.png) The `TFCALL` command is used to execute the JavaScript Function. If the command fails, an error will be returned. Click on the **>_ CLI** button in the lower left-hand corner to open a console window and then run the command shown below. -{{< image filename="/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-3a.png" >}} +![](/images/triggers-and-functions/tf-rdi-3a.png) To update a library you can edit the library code directly in the interface by clicking on the edit (pencil) icon. When you save your changes, the libary will be reloaded. -{{< image filename="/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-4.png" >}} +![](/images/triggers-and-functions/tf-rdi-4.png) ## Uploading an external file Click on the **+ Add Library** button as before and, instead of adding the code directly into the editor, click on the **Upload** button, select the file from your file browser, and then click on **Add Library**. The file needs to contain the header, which contains the engine identifier, the API version, and the library name: `#!js api_version=1.0 name=myFirstLibrary`. -{{< image filename="/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-5.png" >}} +![](/images/triggers-and-functions/tf-rdi-5.png) ## Creating triggers diff --git a/content/operate/oss_and_stack/stack-with-enterprise/install/add-module-to-database.md b/content/operate/oss_and_stack/stack-with-enterprise/install/add-module-to-database.md index 666dc2f390..dbbe44f270 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/install/add-module-to-database.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/install/add-module-to-database.md @@ -36,7 +36,7 @@ In the Redis Software Cluster Manager UI, follow these steps to add modules to a 1. In the **Capabilities** section, select one or more capabilities: - {{Select which capabilities to add to your database.}} + ![Select which capabilities to add to your database.](/images/rs/screenshots/databases/quick-db-capabilities-7-8-2.png) > [!NOTE] > You cannot use RediSearch 1.x and RediSearch 2.x in the same database. diff --git a/content/operate/oss_and_stack/stack-with-enterprise/install/upgrade-module.md b/content/operate/oss_and_stack/stack-with-enterprise/install/upgrade-module.md index afc9cc065f..fbca1321ab 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/install/upgrade-module.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/install/upgrade-module.md @@ -34,7 +34,7 @@ To upgrade a module enabled for a database: 1. Run `rladmin status` to list the databases on the node. 1. Copy the name of the database that uses the module that you want to upgrade. - {{< image filename="/images/rs/rladmin_status.png" >}} + ![](/images/rs/rladmin_status.png) 1. Find the exact module name and version: @@ -44,7 +44,7 @@ To upgrade a module enabled for a database: Here's an example of the JSON file for the RediSearch module: - {{< image filename="/images/rs/module_info.png" >}} + ![](/images/rs/module_info.png) 1. To see the versions of the modules on the cluster, run either: diff --git a/content/operate/oss_and_stack/stack-with-enterprise/json/active-active.md b/content/operate/oss_and_stack/stack-with-enterprise/json/active-active.md index 626c3ccd89..fc0195e4e2 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/json/active-active.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/json/active-active.md @@ -27,7 +27,7 @@ In Redis Software, Active-Active databases created with or upgraded to Redis ver 1. In the **Capabilities** section of the **Create Active-Active database** screen, select **JSON**: - {{Select JSON from the Capabilities section.}} + ![Select JSON from the Capabilities section.](/images/rs/screenshots/databases/active-active-databases/create-a-a-db-json-search.png) > [!NOTE] > When you select **JSON**, **Search and Query** is also selected by default to allow you to index and query JSON documents. If you do not want to use these additional features, you can clear the **Search and Query** check box. diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.0-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.0-release-notes.md index 8b2c45f768..2670c365bf 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.0-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.0-release-notes.md @@ -232,7 +232,7 @@ Finally, RediSearch 2.x keeps its indexes outside of the main Redis key space. I You can read more details in [the RediSearch 2.0 announcement blog post](https://redislabs.com/blog/introducing-redisearch-2-0/), and you can get started by checking out this [quick start blog post](https://redislabs.com/blog/getting-started-with-redisearch-2-0/). -{{Compares the architecture of RediSearch 2.0 to architecture of earlier versions.}} +![Compares the architecture of RediSearch 2.0 to architecture of earlier versions.](/images/modules/redisearch-2-0-architecture.png) ### Details diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.8-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.8-release-notes.md index 056989e031..3539da9767 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.8-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.8-release-notes.md @@ -259,7 +259,7 @@ RedisTimeSeries 1.8 introduces seven highly requested features, performance impr When a time series holds discrete samples of a continuous signal (e.g., temperature), using `avg` to estimate the average value over a given timeframe would produce a good estimate only when the signal is sampled at constant intervals. If, however, samples are available at non-constant intervals (e.g., when some samples are missing), the `twa` aggregator produces a more accurate estimate by averaging samples over time instead of simply averaging the samples. - {{A graph showing the difference between average and time-weighted average.}} + ![A graph showing the difference between average and time-weighted average.](/images/modules/twa.png) This is an extreme example: the signal in the diagram above has 4 samples in its ‘high’ value and 13 samples in its ‘low’ value. However, the period in each of those states is about the same. It is easy to see that the simple average (avg) of all the 17 samples does not represent the signal’s average over time. @@ -271,7 +271,7 @@ RedisTimeSeries 1.8 introduces seven highly requested features, performance impr Using `EMPTY` with the `twa` aggregator allows us to estimate the average of a continuous signal even for buckets where no samples were collected (gap-filling). - {{A graph that illustrates gap-filling.}} + ![A graph that illustrates gap-filling.](/images/modules/GapFilling.png) Consider we want to use [TS.RANGE](/content/commands/ts.range.md) to calculate the average value of each bucket (p1, p2, p3 in the diagram above). Using avg, the value reported for bucket p2 would be NaN, as this bucket contains no samples. If we use `EMPTY` with `twa`, on the other hand, the average value for bucket p2 would be calculated based on the linear interpolation of the value left of p2 and the value right of p2. diff --git a/content/operate/oss_and_stack/stack-with-enterprise/search/config.md b/content/operate/oss_and_stack/stack-with-enterprise/search/config.md index 9084fdc78d..533360aec6 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/search/config.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/search/config.md @@ -37,7 +37,7 @@ For Redis Software, use one of the following methods: In the **Query Performance Factor** section, you can configure settings to improve query performance. See [Configure the query performance factor for Redis Search in Redis Software](/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md) for more information. - {{The Parameters dialog includes sections to edit RediSearch settings and the Query Performance Factor settings.}} + ![The Parameters dialog includes sections to edit RediSearch settings and the Query Performance Factor settings.](/images/rs/screenshots/databases/rs-config-search-params.png) 1. After you finish editing the module's configuration parameters, click **Done** to close the parameter editor. diff --git a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md index 98fea51797..424e6ad30f 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md @@ -84,11 +84,11 @@ To configure the query performance factor: 1. In the **Capabilities** section, click **Add parameters**. - {{The Create database screen with the Add parameters button in the Capabilities section.}} + ![The Create database screen with the Add parameters button in the Capabilities section.](/images/rs/screenshots/databases/rs-qpf-add-parameters-v8.png) 1. In the **Parameters** dialog, use the **Query performance factor** dropdown to select the performance factor value (Standard, 2x, 4x, 6x, 8x, 10x, 12x, 14x, or 16x). - {{The Parameters dialog with the Query performance factor dropdown showing available scaling options.}} + ![The Parameters dialog with the Query performance factor dropdown showing available scaling options.](/images/rs/screenshots/databases/rs-qpf-select-factor-v8.png) 1. Click **Done** to close the parameter editor. @@ -124,7 +124,7 @@ You can use the Cluster Manager UI to configure the query performance factor whe - `32` for **Connections limit** - {{Configure search parameters and query performance factor.}} + ![Configure search parameters and query performance factor.](/images/rs/screenshots/databases/rs-config-query-performance-factor.png) 1. Click **Done** to close the parameter editor. @@ -349,4 +349,4 @@ To monitor a database with a query performance factor configured: - 3rd 600% spike: `memtier_benchmark` search test with threading at a 4x query performance factor (6 CPUs per shard). - {{The Prometheus graph shows three spikes for redis_process_cpu_usage_percent: 100%, another 100%, then 600%.}} + ![The Prometheus graph shows three spikes for redis_process_cpu_usage_percent: 100%, another 100%, then 600%.](/images/rs/screenshots/monitor-rs-scalable-search-cpu-usage.png) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/search/redisearch-2-upgrade.md b/content/operate/oss_and_stack/stack-with-enterprise/search/redisearch-2-upgrade.md index 206bbd34fe..31a8c58cea 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/search/redisearch-2-upgrade.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/search/redisearch-2-upgrade.md @@ -64,7 +64,7 @@ To replicate a RediSearch 1.x database to a RediSearch 2.x database: 1. In **redis modules**, select the **Add module** button. - {{< image filename="/images/rs/upgrade_module.png" >}} + ![](/images/rs/upgrade_module.png) 1. Use the file browser to select the module package and upload it to the cluster. @@ -76,13 +76,15 @@ To replicate a RediSearch 1.x database to a RediSearch 2.x database: 1. Select the **Add** button: - {{The Add icon}} + ![The Add icon](/images/rs/icon_add.png) + {width="30px"} 1. Select **RediSearch 2** from the dropdown list. 1. Select the **OK** button to confirm: - {{The Save icon}} + ![The Save icon](/images/rs/icon_save.png) + {width="30px"} 1. Select the **Activate** button to create the database. diff --git a/content/operate/oss_and_stack/stack-with-enterprise/stack-quickstart.md b/content/operate/oss_and_stack/stack-with-enterprise/stack-quickstart.md index efc3363684..0d120006b8 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/stack-quickstart.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/stack-quickstart.md @@ -38,7 +38,8 @@ To create a new subscription: 1. Select the **New subscription** button: - {{The New subscriptions button in the admin console menu.}} + ![The New subscriptions button in the admin console menu.](/images/rc/button-subscription-new.png) + {width="150px"} 1. Configure your subscription: @@ -50,7 +51,8 @@ To create a new subscription: 1. Select the **Create subscription** button: - {{The Create Subscription button.}} + ![The Create Subscription button.](/images/rc/button-subscription-create.png) + {width="150px"} ### Create a Redis Stack database @@ -58,7 +60,8 @@ After you create a subscription, follow these steps to create a Redis Stack data 1. Select the **New database** button: - {{The New Database button creates a new database for your subscription.}} + ![The New Database button creates a new database for your subscription.](/images/rc/button-database-new.png) + {width="120px"} 1. In **General** settings, enter a **Database name**. @@ -66,7 +69,8 @@ After you create a subscription, follow these steps to create a Redis Stack data 1. Select the **Activate database** button: - {{Use the Activate database button to create and activate your database.}} + ![Use the Activate database button to create and activate your database.](/images/rc/button-database-activate.png) + {width="150px"} ### Connect to the database diff --git a/content/operate/oss_and_stack/stack-with-enterprise/timeseries/_index.md b/content/operate/oss_and_stack/stack-with-enterprise/timeseries/_index.md index 23f6e25b90..89d19e87f7 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/timeseries/_index.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/timeseries/_index.md @@ -80,7 +80,7 @@ Here's an example of [aggregation](/content/develop/data-types/timeseries/_index Redis Open Source comes with several integrations into existing time series tools. One such integration is our [RedisTimeSeries adapter](https://github.com/RedisTimeSeries/prometheus-redistimeseries-adapter) for [Prometheus](https://prometheus.io/), which keeps all your monitoring metrics inside time series while leveraging the entire [Prometheus ecosystem](https://prometheus.io/docs/prometheus/latest/storage/#remote-storage-integrations). -{{< image filename="/images/rs/TimeSeries-integrations.png" >}} +![](/images/rs/TimeSeries-integrations.png) Furthermore, we also created direct integrations for [Grafana](https://github.com/RedisTimeSeries/grafana-redistimeseries). [This repository](https://github.com/RedisTimeSeries/prometheus-demos) contains a docker-compose setup of RedisTimeSeries, its remote write adaptor, Prometheus and [Grafana](https://grafana.com/). It also comes with a set of data generators and pre-built Grafana dashboards. @@ -90,21 +90,21 @@ Furthermore, we also created direct integrations for [Grafana](https://github.co Redis streams allow you to add several field value pairs in a message for a given timestamp. For each device, we collected 10 metrics that were modeled as 10 separate fields in a single stream message. -{{< image filename="/images/rs/TimeSeries-modeling1.png" >}} +![](/images/rs/TimeSeries-modeling1.png) For sorted sets, we modeled the data in two different ways. For "Sorted set per device", we concatenated the metrics and separated them out by colons, e.g. `"::: … :"`. -{{< image filename="/images/rs/TimeSeries-modeling2.png" >}} +![](/images/rs/TimeSeries-modeling2.png) Of course, this consumes less memory but needs more CPU cycles to get the correct metric at read time. It also implies that changing the number of metrics per device isn’t straightforward, which is why we also benchmarked a second sorted set approach. In "Sorted set per metric," we kept each metric in its own sorted set and had 10 sorted sets per device. We logged values in the format `":"`. -{{< image filename="/images/rs/TimeSeries-modeling3.png" >}} +![](/images/rs/TimeSeries-modeling3.png) Another alternative approach would be to normalize the data by creating a hash with a unique key to track all measurements for a given device for a given timestamp. This key would then be the value in the sorted set. However, having to access many hashes to read a time series would come at a huge cost during read time, so we abandoned this path. Each time series holds a single metric. We chose this design to maintain the Redis principle that a larger number of small keys is better than a fewer number of large keys. -{{< image filename="/images/rs/TimeSeries-modeling4.png" >}} +![](/images/rs/TimeSeries-modeling4.png) Our benchmark did not utilize the out-of-the-box secondary indexing capabilities of time series. Redis keeps a partial secondary index in each shard, and since the index inherits the same hash-slot of the key it indexes, it is always hosted on the same shard. This approach would make the setup for native data structures even more complex to model, so for the sake of simplicity, we decided not to include it in our benchmarks. Additionally, while Redis Software can use the [proxy](https://redis.com/redis-enterprise/technology/redis-enterprise-cluster-architecture/) to fan out requests for commands like [TS.MGET](/content/commands/ts.mget.md) and [TS.MRANGE](/content/commands/ts.mrange.md) to all the shards and aggregate the results, we chose not to exploit this advantage in the benchmark either. @@ -121,7 +121,7 @@ Ingestion details of each approach: | **Metrics per request** | 5000 | 5000 | 5000 | 500 | | **# keys** | 4000 | 40000 | 4000 | 40000 | -{{< image filename="/images/rs/TimeSeries-DataIngestion.png" >}} +![](/images/rs/TimeSeries-DataIngestion.png) All our ingestion operations were executed at sub-millisecond latency. Although both used the same Rax data structure, the time series approach has slightly higher throughput than Redis streams. @@ -137,7 +137,7 @@ The read query we used in this benchmark queried a single time series and aggreg For the Redis streams and sorted sets approaches, we created [the following LUA scripts](https://gist.github.com/itamarhaber/0107020b91c71cb52e57e9a9c890c24e). The client once again had 8 threads and 50 connections each. Since we executed the same query, only a single shard was hit, and in all four cases this shard maxed out at 100% CPU. -{{< image filename="/images/rs/TimeSeries-ReadQueries.png" >}} +![](/images/rs/TimeSeries-ReadQueries.png) This is where you can see the real power of having dedicated data structure for a given use case with a toolbox that runs alongside it. Using time series exceeds all other approaches and is the only one to achieve sub-millisecond response times. @@ -147,7 +147,7 @@ For both the Redis streams and sorted set approaches, the samples were stored as Time series can dramatically reduce the memory consumption when compared against both sorted set approaches. Given the unbounded nature of time series data, this is typically a critical criteria to evaluate - the overall data set size that needs to be retained in memory. Redis streams reduces the memory consumption further but would be equal or higher than time series when more digits for a higher precision would be required. -{{< image filename="/images/rs/TimeSeries-UsedMemory.png" >}} +![](/images/rs/TimeSeries-UsedMemory.png) ## More info diff --git a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-0.png b/static/images/triggers-and-functions/tf-rdi-0.png similarity index 100% rename from content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-0.png rename to static/images/triggers-and-functions/tf-rdi-0.png diff --git a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-1.png b/static/images/triggers-and-functions/tf-rdi-1.png similarity index 100% rename from content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-1.png rename to static/images/triggers-and-functions/tf-rdi-1.png diff --git a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-2.png b/static/images/triggers-and-functions/tf-rdi-2.png similarity index 100% rename from content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-2.png rename to static/images/triggers-and-functions/tf-rdi-2.png diff --git a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-3.png b/static/images/triggers-and-functions/tf-rdi-3.png similarity index 100% rename from content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-3.png rename to static/images/triggers-and-functions/tf-rdi-3.png diff --git a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-3a.png b/static/images/triggers-and-functions/tf-rdi-3a.png similarity index 100% rename from content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-3a.png rename to static/images/triggers-and-functions/tf-rdi-3a.png diff --git a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-4.png b/static/images/triggers-and-functions/tf-rdi-4.png similarity index 100% rename from content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-4.png rename to static/images/triggers-and-functions/tf-rdi-4.png diff --git a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-5.png b/static/images/triggers-and-functions/tf-rdi-5.png similarity index 100% rename from content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/images/tf-rdi-5.png rename to static/images/triggers-and-functions/tf-rdi-5.png