Key Concepts
Command
Redis commands consist of a command name followed by arguments (e.g.,
GET mykey).Response Types
Commands return different types: strings, integers, lists, nil, or errors.
Database
Commands execute against the selected database (0-15). Use SELECT to switch.
History
Previous commands are saved in session history for quick recall.
Required Permissions
| Action | Permission |
|---|---|
| Execute commands | iam:project:infrastructure:redis:write |
How to Execute a Command
Keyboard Shortcuts
| Key | Action |
|---|---|
Enter | Execute the current command |
↑ (Arrow Up) | Previous command from history |
↓ (Arrow Down) | Next command in history |
Quick Commands
Pre-configured commands for common operations:| Command | Description |
|---|---|
PING | Test connection (returns PONG) |
INFO | Server information and statistics |
DBSIZE | Number of keys in current database |
KEYS * | List all keys (use with caution) |
SCAN 0 | Scan keys safely with cursor |
CONFIG GET * | Get all configuration parameters |
CLIENT LIST | List connected clients |
SLOWLOG GET 10 | Recent slow log entries |
MEMORY STATS | Memory usage statistics |
TIME | Current server time |
Response Types
| Type | Description | Example |
|---|---|---|
| string | Simple string response | "OK", "PONG" |
| integer | Numeric response | (integer) 42 |
| list | Array of values | Numbered list of items |
| dict | Key-value pairs | Object properties |
| null | No value | (nil) |
Common Commands
Key Operations
| Command | Description |
|---|---|
GET key | Get value of a key |
SET key value | Set key to value |
DEL key | Delete a key |
EXISTS key | Check if key exists |
TYPE key | Get key type |
TTL key | Get time to live in seconds |
EXPIRE key seconds | Set expiration |
String Operations
| Command | Description |
|---|---|
SET key value | Set string value |
GET key | Get string value |
INCR key | Increment by 1 |
DECR key | Decrement by 1 |
APPEND key value | Append to string |
Hash Operations
| Command | Description |
|---|---|
HSET key field value | Set hash field |
HGET key field | Get hash field |
HGETALL key | Get all fields and values |
HDEL key field | Delete hash field |
List Operations
| Command | Description |
|---|---|
LPUSH key value | Push to left (head) |
RPUSH key value | Push to right (tail) |
LPOP key | Pop from left |
RPOP key | Pop from right |
LRANGE key 0 -1 | Get all elements |
Set Operations
| Command | Description |
|---|---|
SADD key member | Add member to set |
SMEMBERS key | Get all members |
SISMEMBER key member | Check membership |
SREM key member | Remove member |
Server Commands
| Command | Description |
|---|---|
INFO | Server information |
INFO memory | Memory section only |
CONFIG GET parameter | Get config value |
CONFIG SET parameter value | Set config value |
FLUSHDB | Delete all keys in database |
FLUSHALL | Delete all keys in all databases |
How to Use Command History
Command history is stored in your browser session. It clears when you close the browser or click Clear.
How to Copy Results
How to Clear History
Troubleshooting
Command returns error
Command returns error
- Check command syntax
- Verify key exists (for read commands)
- Check argument count and types
- Some commands require specific Redis versions
Cannot execute commands
Cannot execute commands
- You need write permission for CLI access
- Check if connection is active
- Verify network connectivity to Redis
Command taking too long
Command taking too long
- Large dataset operations take time
- KEYS * on large databases is slow
- Use SCAN instead of KEYS for large datasets
- Check slow log for details
Unexpected response format
Unexpected response format
- Different commands return different types
- Arrays show numbered lists
- Nil means the key doesn’t exist
- Check Redis documentation for expected return type
History not persisting
History not persisting
- History is session-only, not persisted to server
- Refreshing the page clears history
- Use a local Redis CLI for persistent history
Cannot see write commands
Cannot see write commands
- You need
iam:project:infrastructure:redis:writepermission - Contact your administrator for access
FAQ
Is this the same as redis-cli?
Is this the same as redis-cli?
This provides similar functionality to the
redis-cli command-line tool but runs in your browser. It supports most commands but may not support interactive features like MONITOR or SUBSCRIBE.Can I run multiple commands at once?
Can I run multiple commands at once?
Commands are executed one at a time. For bulk operations, consider using scripts or the native redis-cli with pipelines.
Are my commands logged?
Are my commands logged?
Commands may be logged for audit purposes. Avoid entering sensitive data like passwords in command arguments.
Why can't I use SUBSCRIBE or MONITOR?
Why can't I use SUBSCRIBE or MONITOR?
These commands require persistent connections and streaming responses, which are not supported in this web interface. Use a native Redis client for these features.
What happens if I run FLUSHDB?
What happens if I run FLUSHDB?
FLUSHDB deletes all keys in the current database immediately and permanently. There is no confirmation prompt. Use with extreme caution.
Can I script multiple commands?
Can I script multiple commands?
Use Lua scripting with
EVAL for atomic multi-command operations. Example: EVAL "return redis.call('GET', KEYS[1])" 1 mykeyHow do I switch databases?
How do I switch databases?
Use the database dropdown in the toolbar, or execute
SELECT <db-number> command.What commands are not supported?
What commands are not supported?
Interactive commands (MONITOR, SUBSCRIBE, PSUBSCRIBE) and blocking commands with infinite timeout may not work properly in the web interface.
Best Practices
Safety
- Test commands on non-production first
- Avoid KEYS * on large databases
- Use SCAN for iterating keys
- Never run FLUSHDB/FLUSHALL without verification
- Be careful with CONFIG SET changes
Performance
- Use specific key patterns instead of wildcards
- Paginate large result sets
- Prefer EXISTS over GET for existence checks
- Use MGET/MSET for multiple keys
Debugging
- Use TYPE to verify key types
- Check TTL to understand expiration
- Use OBJECT ENCODING for internal representation
- Review MEMORY USAGE for key size
Commands to Avoid in Production
| Command | Risk | Alternative |
|---|---|---|
KEYS * | Blocks server | SCAN |
FLUSHDB | Data loss | Selective DEL |
FLUSHALL | All data loss | None |
DEBUG * | Server impact | INFO |
SHUTDOWN | Server stops | Admin access |