From c7d446383717a3391e4bf25fc89add91988dcba6 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:45:42 -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 066741cef..063c13da6 100644
--- a/content/integrate/prometheus-with-redis-enterprise/observability.md
+++ b/content/integrate/prometheus-with-redis-enterprise/observability.md
@@ -240,7 +240,7 @@ excess inefficient Redis operations, and hot master shards.
 The Redis Enterprise database dashboard indicates the total number of connections to the database.
 
 You should monitor this connection count metric with both a minimum and maximum number of connections in mind.
-Based on the number of application instances connecting to Redis (and whether your application uses connection pooling),
+Based on the number of application instances connecting to Redis (and whether your application uses [connection pooling]({{< relref "/develop/clients/pools-and-muxing" >}})),
 you should have a rough idea of the minimum and maximum number of connections you expect to see for any given database.
 This number should remain relatively constant over time.