Redis operations workflows

Explore the keyspace

1. Select a connection and database.
2. Choose the namespace tree or virtualized flat list based on scale.
3. Narrow results with exact scans, search history, or team-saved filters.
4. Open a key tab to inspect type, TTL, encoding, and content.

Large keyspaces can use server-side namespace summaries and resumable scan jobs. Avoid unbounded wildcard scans during production peaks.

Edit data

The workspace supports strings, hashes, lists, sets, sorted sets, streams, and RedisJSON. Binary values can use Text, Hex, or Base64 input. The advanced viewer handles JSON, MsgPack, gzip, deflate, and other formats.

Before writing, confirm:

• The current connection, database, and key name.
• Whether TTL must be preserved or changed.
• Whether encoding matches the application producer.
• The number of keys affected by bulk delete, expire, or persist.

Runtime diagnostics

• Use slowlog to identify expensive commands.
• Inspect clients and confirm before killing abnormal connections.
• Use memory analysis for large keys and costly structures.
• Run command monitoring only for short windows to limit overhead.
• Review and set notify-keyspace-events carefully before monitoring notifications.

Advanced operations

List trim/pop, set algebra and store, sorted-set range deletes, stream consumer groups, bitmap, HyperLogLog, and Geo operations modify data. Prefer previews, bound each batch, and keep an application-level rollback plan.