Conversation
RC: Seamless endpoint migration phase A
andy-stark-redis
left a comment
andy-stark-redis
left a comment
There was a problem hiding this comment.
Embed paths need to be fixed but otherwise LGTM.
|
|
||
| ### Dynamic endpoints | ||
|
|
||
| As of {{RELEASE DATE}}, Redis Cloud now generates dynamic endpoints for all databases. Databases created before {{RELEASE DATE}} can still view both static endpoints and dynamic endpoints. Static endpoints will still work at this time, but they may be deprecated in the future. |
There was a problem hiding this comment.
Just checking that the {{ RELEASE DATE}} still isn't known yet?
There was a problem hiding this comment.
current eta is March 22
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
kaitlynmichael
left a comment
kaitlynmichael
left a comment
There was a problem hiding this comment.
Didn't get through it all yet, but here's a few small things.
Co-authored-by: Kaitlyn Michael <76962844+kaitlynmichael@users.noreply.github.com>
andy-stark-redis
left a comment
andy-stark-redis
left a comment
There was a problem hiding this comment.
A few minor style suggestions, otherwise LGTM.
| @@ -0,0 +1,3 @@ | |||
| In the **Metrics** tab of your database, select **Connect to Prometheus > Copy Prometheus endpoint** to save your prometheus endpoint to the clipboard. | |||
There was a problem hiding this comment.
maybe write that it's also avaialble to retrieve through the database API
|
|
||
| ### Dynamic endpoints | ||
|
|
||
| As of {{RELEASE DATE}}, Redis Cloud now generates dynamic endpoints for all databases. Databases created before {{RELEASE DATE}} can still view both static endpoints and dynamic endpoints. Static endpoints will still work at this time, but they may be deprecated in the future. |
There was a problem hiding this comment.
current eta is March 22
|
|
||
| ### Dynamic endpoints | ||
|
|
||
| As of {{RELEASE DATE}}, Redis Cloud now generates dynamic endpoints for all databases. Databases created before {{RELEASE DATE}} can still view both static endpoints and dynamic endpoints. Static endpoints will still work at this time, but they may be deprecated in the future. |
There was a problem hiding this comment.
I think we need a section in the docs on "Dynamic endpoints" (maybe in the configuration page, or connectivity?). That would explain a few sentences what Dynamic endpoints are and that you can redirect endpoints, alias of the dB endpoint, bla bla bla.
And link it from here and from other places in the docs
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
🛡️ Jit Security Scan Results
✅ No security findings were detected in this PR
Security scan by Jit
|
| To illustrate, suppose you want to migrate a 1 GB source database without replication to a target database with replication enabled. Here, the target database memory limit should be at least 2.5 GB to avoid data loss. | ||
|
|
||
| Once the databases are synced, you can disable Active-Passive for the target database. Before doing so, however, verify that apps and other connections have switched to the target database; otherwise, you may lose data. | ||
|
|
There was a problem hiding this comment.
Here I want to add a note regarding the API. I'll describe the process and you will do your magic to make it clear and put here where you think:)
- In the UI, the process is as you described. You just search for your DB in the search
- Using the API is different. Because the Dynamic endpoint can move, the user needs to give us the cluster endpoint and not dynamic one. In the UI we don't need to do adjustments because we just choose the actual DB.. not the endpoint
- What we did:
- We exposed a new attribute in the API on the GET DB call: replicaAsSourceEndpoints
- So the customer will need to use those endpoints if they want to set the replica of the program programmatically.
There was a problem hiding this comment.
We should definitely put this in the API docs. I'll work on adding this to the user docs later.
4 participants
Note
Low Risk
Low risk: documentation-only changes that add new guidance and cross-links; no product code or API behavior is modified.
Overview
Adds documentation for dynamic endpoints and a new endpoint redirection workflow, including prerequisites/compatibility constraints, step-by-step console instructions, and a 24-hour revert window.
Updates migration/upgrade/connect docs to reference redirecting dynamic endpoints as a post-migration step (including port-matching guidance for Essentials->Pro) and introduces a March 2026 changelog entry announcing the feature.
Standardizes how to obtain the Redis Cloud Prometheus endpoint by adding a reusable embed and reusing it across Prometheus, New Relic, Dynatrace, and
Monitor performancepages.Written by Cursor Bugbot for commit 807f849. This will update automatically on new commits. Configure here.