Redis Key Explorer

Route Scope

Redis explorer route:

• /$orgSlug/c/$connectionId/redis-keys

Search Behavior

Key search endpoint:

• GET /api/c/:connectionId/redis-keys/search

Features:

• pattern search (* by default)
• cursor-based pagination (SCAN)
• optional excludeBull=true
• key type, TTL, and best-effort memory usage

pageSize is a scan target, not a strict result limit; Redis SCAN can return more keys in a batch. Continue with the returned cursor until it is "0". total, when available, is the database's key count, not the number matching the search pattern. TTL -1 means no expiration, and -2 means the key no longer exists.

Key Value Inspection

Value endpoint:

• GET /api/c/:connectionId/redis-keys/value/:key

Type-aware parsing:

• string (attempt JSON parse)
• hash
• list
• set
• zset
• stream

Lists and sorted sets support offset and limit. Hash inspection reads the whole hash; set and stream inspection is bounded but does not provide a resumable cursor. Large collections may therefore show only a sample.

Deletion Safety Rule

Delete endpoint:

• DELETE /api/c/:connectionId/redis-keys/:key

Durabull blocks deletion of keys starting with bull: or bullmq:. The excludeBull=true search filter uses the same prefixes. Custom BullMQ prefixes are not covered by this guard; manage those keys through queue and job operations too.

Reason:

• Bull queue internals should be managed via queue/job operations, not raw key deletion.

Good Practices

• Use key explorer for app-level cache/session/config keys.
• Keep BullMQ internal cleanup within queue/job workflows.
• Prefer pattern filtering to reduce broad scans in large keyspaces.