RedScout is a Redis monitoring tool that provides namespace-level insights into your Redis database unlike
traditional tools that focus more on server-level metrics. It breaks down memory usage, key TTLs, and OP/s by logical
namespaces, giving you clear visibility into which parts of your application are driving Redis usage. RedScout can also
handle deeply nested key patterns like user:<user-id>:messages:unread
or user:<user-id>:order:<order-id>:status
,
helping you pinpoint hotspots with precision.
RedScout leverages three core Redis commands: SCAN
, MEMORY USAGE
, and MONITOR
to assemble a namespace-level
view of your cache. On top of these, it accepts configurable inputs such as a custom delimiter for splitting key
hierarchies and regular expressions to automatically identify and infer id components within your keys.
- Redis Version: 4.0.0 or higher (required for
MEMORY USAGE
command)
Download the appropriate binary for your platform from the releases page.
./redscout \
-host redis.example.com \
-port 6379 \
-password "your-password" \
-tls true \
-monitor-duration 30 \
-scan-size 10000
Flag | Type | Default | Description |
---|---|---|---|
-host |
string | (empty) | Redis host address |
-port |
int | 6379 |
Redis port number |
-username |
string | default |
Redis username for authentication |
-password |
string | (empty) | Redis password for authentication |
-db |
int | 0 |
Redis database number to analyze |
-tls |
string | false |
Use TLS for Redis connection (true/false) |
Flag | Type | Default | Description |
---|---|---|---|
-delimiter |
string | : |
Delimiter for separating Redis keys into namespaces |
-scan-size |
int | 5000 |
Number of keys to scan |
-monitor-duration |
int | 10 |
Duration in seconds to run the monitor command |
-refresh-interval |
int | 5 |
Interval in seconds between Redis info refreshes |
-id-regex |
string | (empty) | Space-separated list of regex patterns to infer IDs from keys |
Flag | Type | Default | Description |
---|---|---|---|
-logs-dir |
string | OS's temp dir | Directory to store temporary analysis logs |
- Uses Redis MONITOR command, so be careful when using in production environments
- Results are estimates based on sampling, not exhaustive key scanning