Skip to content

Commit db1fd06

Browse files
Update content/integrate/prometheus-with-redis-enterprise/observability.md
Co-authored-by: andy-stark-redis <[email protected]>
1 parent 2078c97 commit db1fd06

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

content/integrate/prometheus-with-redis-enterprise/observability.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -440,9 +440,9 @@ This section defines each of these patterns and describes how to diagnose and mi
440440

441441
Not all Redis operations are equally efficient.
442442
The most efficient Redis operations are O(1) operations; that is, they have a constant time complexity.
443-
Example of such operations include [GET](https://redis.io/docs/latest/commands/get/),
444-
[SET](https://redis.io/docs/latest/commands/set/), [SADD](https://redis.io/docs/latest/commands/sadd/),
445-
and [HSET](https://redis.io/docs/latest/commands/hset/).
443+
Example of such operations include [GET]({{< relref "/commands/get" >}}),
444+
[SET]({{< relref "/commands/set" >}}), [SADD]({{< relref "/commands/sadd" >}}),
445+
and [HSET]({{< relref "/commands/hset" >}}).
446446

447447
These constant time operations are unlikely to cause high CPU utilization. **Note:** Even so,
448448
it's still possible for a high rate of constant time operations to overwhelm an underprovisioned database.

0 commit comments

Comments
 (0)