You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/operate/rc/databases/rdi/setup.md
+9-2Lines changed: 9 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ In the [AWS Management Console](https://console.aws.amazon.com/), use the **Serv
81
81
-**Target type**: Select **Instances**.
82
82
-**Protocol : Port**: Select **TCP**, and then enter the port number where your database is exposed.
83
83
- The **IP address type** and **VPC** should be selected already and match the VPC you selected earlier.
84
-
1. In **Register targets**, select the EC2 instance that runs your source database, enter the port, and select **Include as pending below**. Then, select **Create target group** to create your target group. Return **Listeners and routing** in the Network Load Balancer setup.
84
+
1. In **Register targets**, select the EC2 instance that runs your source database, enter the port, and select **Include as pending below**. Then, select **Create target group** to create your target group. Return to **Listeners and routing** in the Network Load Balancer setup.
85
85
1. Set the following **Listener** properties:
86
86
-**Protocol**: Select **TCP**.
87
87
-**Port**: Enter your source database's port.
@@ -129,6 +129,13 @@ To do this:
129
129
130
130
In the [AWS Management Console](https://console.aws.amazon.com/), use the **Services** menu to locate and select **Database** > **Aurora and RDS**. [Create an RDS proxy](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/rds-proxy-creating.html) that can access your database.
131
131
132
+
The Proxy's IAM role must have the following permissions to access the database using the credentials secret and encryption key:
133
+
-`secretsmanager:GetSecretValue`
134
+
-`secretsmanager:DescribeSecret`
135
+
-`kms:Decrypt`
136
+
137
+
You can set the proxy's IAM role during creation in the **Authentication** section.
In the [AWS Management Console](https://console.aws.amazon.com/), use the **Services** menu to locate and select **Compute** > **EC2**. [Create a network load balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/create-network-load-balancer.html#configure-load-balancer) with the following settings:
@@ -144,7 +151,7 @@ In the [AWS Management Console](https://console.aws.amazon.com/), use the **Serv
144
151
-**Target type**: Select **IP Addresses**.
145
152
-**Protocol : Port**: Select **TCP**, and then enter the port number where your database is exposed.
146
153
- The **IP address type** and **VPC** should be selected already and match the VPC you selected earlier.
147
-
1. In **Register targets**, enter the static IP address of your RDS proxy, enter the port, and select **Include as pending below**. Then, select **Create target group** to create your target group. Return **Listeners and routing** in the Network Load Balancer setup.
154
+
1. In **Register targets**, enter the static IP address of your RDS proxy, enter the port, and select **Include as pending below**. Then, select **Create target group** to create your target group. Return to **Listeners and routing** in the Network Load Balancer setup.
148
155
To get the static IP address of your RDS Proxy, run the following command on an EC2 instance in the same VPC as the Proxy:
Copy file name to clipboardExpand all lines: content/operate/rc/databases/rdi/view-edit.md
+10Lines changed: 10 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -99,6 +99,16 @@ At this point, the data pipeline will apply the changes. If you selected **Reset
99
99
100
100
If you selected **Apply to new data changes only**, the data pipeline will enter the *change streaming* phase without ingesting data.
101
101
102
+
## View metrics endpoints
103
+
104
+
You can use [Prometheus and Grafana]({{< relref "/integrate/prometheus-with-redis-cloud/" >}}) to track and display metrics for the data pipeline.
105
+
106
+
To view the metrics endpoints for the source collector and pipeline processor, go to the **Data pipeline** tab and select **More actions**, and then **Show metrics**. You can add these endpoints as a Prometheus target to start tracking your RDI metrics.
107
+
108
+
Prometheus endpoints are exposed on Redis Cloud's internal network. To access this network, enable [VPC peering]({{< relref "/operate/rc/security/vpc-peering" >}}) or [AWS Transit Gateway]({{< relref "/operate/rc/security/aws-transit-gateway" >}}). See [Prometheus and Grafana with Redis Cloud]({{< relref "/integrate/prometheus-with-redis-cloud/" >}}) for more information.
109
+
110
+
For more information about available RDI metrics, see [Observability]({{< relref "/integrate/redis-data-integration/observability" >}}).
111
+
102
112
## Reset data pipeline
103
113
104
114
Resetting the data pipeline creates a new baseline snapshot from the current state of your source database, and re-processes the data from the source database to the target Redis database. You may want to reset the pipeline if the source and target databases were disconnected or you made large changes to the data pipeline.
0 commit comments