From 6b239436c9e87ef3110a32ef78aa48266b826a15 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:52:12 -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> --- .../prometheus-with-redis-enterprise/observability.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/integrate/prometheus-with-redis-enterprise/observability.md b/content/integrate/prometheus-with-redis-enterprise/observability.md index 40812bc08..ba2a479b8 100644 --- a/content/integrate/prometheus-with-redis-enterprise/observability.md +++ b/content/integrate/prometheus-with-redis-enterprise/observability.md @@ -338,8 +338,7 @@ networking issue. | ------ | ------ | :------ | |Slow database operations | Confirm that there are no excessive slow operations in the Redis slow log. | If possible, reduce the number of slow operations being sent to the database.
If this not possible, consider increasing the number of shards in the database. | |Increased traffic to the database | Review the network traffic and the database operations per second chart to determine if increased traffic is causing the latency. | If the database is underprovisioned due to increased traffic, consider increasing the number of shards in the database. | -|Insufficient CPU | Check to see if the CPU utilization is increasing. | Confirm that slow operations are not causing the high CPU utilization. -If the high CPU utilization is due to increased load, consider adding shards to the database. | +|Insufficient CPU | Check to see if the CPU utilization is increasing. | Confirm that slow operations are not causing the high CPU utilization. If the high CPU utilization is due to increased load, consider adding shards to the database. | ## Cache hit rate