# ERR: Latency monitor threshold exceeded for command 'GET'

- **ID:** `redis/latency-monitor-threshold-exceeded`
- **Domain:** redis
- **Category:** performance_error
- **Verification:** ai_generated
- **Fix Rate:** 85%

## Root Cause

A command execution time exceeded the latency-monitor-threshold, indicating a slow operation or system overload.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| Redis 6.2 | active | — | — |
| Redis 7.0 | active | — | — |
| Redis 7.2 | active | — | — |

## Workarounds

1. **Identify the slow command using SLOWLOG GET and optimize it (e.g., reduce key size, use pipelining, or split large operations).** (85% success)
   ```
   Identify the slow command using SLOWLOG GET and optimize it (e.g., reduce key size, use pipelining, or split large operations).
   ```
2. **Run: redis-cli --latency to check network latency; if high, move Redis closer to the client or use a faster network.** (70% success)
   ```
   Run: redis-cli --latency to check network latency; if high, move Redis closer to the client or use a faster network.
   ```

## Dead Ends

- **Increase latency-monitor-threshold to a very high value** — Masking the symptom without addressing root cause (e.g., slow commands, large keys, or network issues). (40% fail)
- **Disable latency monitoring entirely with CONFIG SET latency-monitor-threshold 0** — Removes visibility into performance issues, making debugging harder later. (30% fail)