From f1ec9140037c80d8eb7805d3f45b2d140269c2eb Mon Sep 17 00:00:00 2001
From: mich-elle-luna <153109578+mich-elle-luna@users.noreply.github.com>
Date: Mon, 2 Dec 2024 15:55:52 -0800
Subject: [PATCH] Update
 content/integrate/prometheus-with-redis-enterprise/observability.md

Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
---
 .../integrate/prometheus-with-redis-enterprise/observability.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/integrate/prometheus-with-redis-enterprise/observability.md b/content/integrate/prometheus-with-redis-enterprise/observability.md
index c5dcf1452..30846a715 100644
--- a/content/integrate/prometheus-with-redis-enterprise/observability.md
+++ b/content/integrate/prometheus-with-redis-enterprise/observability.md
@@ -457,7 +457,7 @@ a large number of elements (for example, a list with 1 million elements).
 However, the [KEYS]({{< relref "/commands/keys" >}}) command should almost never be run against a
 production system, since returning a list of all keys in a large Redis database can cause significant slowdowns
 and block other operations. If you need to scan the keyspace, especially in a production cluster, always use the
-[SCAN](https://redis.io/docs/latest/commands/scan) command instead.
+[SCAN]({{< relref "/commands/scan" >}}) command instead.
 
 ### Troubleshooting