Redis Key Name Validator

Paste key names, one per line. Redis accepts almost any byte sequence as a key, so nothing here is about validity: it is about names that work in a shell, in a log, and on a cluster.

Paste below, or drop a file anywhere on this panel

Or drop a file anywhere on this panel. Nothing is uploaded: the analysis runs in this tab.

The answer appears here

Paste on the left and press Check. Nothing leaves this tab.

Examples

Real input you can load into the tool above. Each one shows a different thing going wrong, because that is what the tool is for.

Every key in one slot

A constant hash tag puts the whole keyspace on a single node

{app}:user:1
{app}:user:2
{app}:user:3
{app}:user:4
{app}:user:5
{app}:user:6

A key with a space

Legal, and painful in every shell and every log

user:1
a key with spaces
session:abc

Common mistakes

These are the ones that fail silently. The config is accepted, nothing raises an error, and the consequence arrives later.

  1. Using one hash tag for every key

    It forces the whole keyspace into one slot on one node, so the cluster cannot balance.

    Instead:Tag by the group that must stay together, such as a tenant id.

  2. Building a key from unsanitised user input

    A newline or a null byte produces a key nobody can see in any diagnostic.

    Instead:Strip control characters, or hash the variable part.

  3. Assuming {} makes a hash tag

    An empty brace pair is not a tag, and neither is an unclosed brace. The whole key is hashed instead.

    Instead:Put a real value between the braces.

  4. Mixing colons, dots and dashes as separators

    Prefix patterns written for one convention silently miss the others.

    Instead:Pick one separator and use it everywhere.

Redis accepts any bytes, and that is the problem

A key can contain a newline, a space or a null byte and Redis will store and return it perfectly. Everything else in your stack will not cope as well.

Control characters make a key invisible in every diagnostic

A key with a trailing newline looks identical to one without in redis-cli output, in MONITOR, in SLOWLOG and in your logs. It stores and retrieves correctly, so the bug is a lookup that fails for no visible reason, and a difference nobody can see is one nobody can fix.

A hash tag decides which node the key lives on

Only the text between the first brace and the first closing brace after it is hashed. That is what makes multi-key commands possible on a cluster. Using the same tag for every key puts the entire keyspace on one node, so the cluster cannot balance and one node carries all the traffic.

Braces have three rules and two of them surprise people

An empty pair is not a tag. An unclosed brace is not a tag. Only the first brace, paired with the first closing brace after it, counts. A key that looks tagged may not be, and it will land in a different slot than the one you intended.

Key names cost memory, once per key

The name is stored in full, in memory, for every key, and it is copied into every reply and every log line. At tens of millions of keys the names alone become a measurable fraction of the dataset. The limit is 512 MB, so this is a cost question rather than a validity one.

Mixed separators break prefix matching

A SCAN pattern written for one convention silently misses keys following another. Pick one, conventionally the colon, and use it everywhere.

More redis tools

Redis Hash Slot Calculator Which of the 16,384 slots does this key land in? Redis Hash Tag Tester Will these keys survive a multi-key command? Redis RESP Protocol Decoder Read what the server actually sent Redis RESP2 vs RESP3 Reply Decoder What the same reply looks like on each protocol Redis Command to RESP Exactly what your client puts on the socket Redis Glob Pattern Tester Redis globs are not shell globs Redis Connection URL Parser The path is the database number Redis Memory Unit Converter 1g and 1gb are not the same number Redis TTL Converter -1 and -2 are not durations Redis Stream ID Parser The first half is a millisecond timestamp redis.conf Validator Will Redis start with this file? Redis Production Config Linter The settings that cause incidents redis.conf to CONFIG SET Which of these can you change without a restart? Redis ACL Rule Decoder What does this user actually get? Redis ACL Validator Find the rule that does nothing Redis INFO Analyzer The numbers INFO does not print Redis SLOWLOG Analyzer What blocked everyone else Redis CLUSTER NODES Parser Read the topology, and find the gap Redis Cluster Slot Distribution Who owns how much, and what is missing Redis Keyspace Notification Flags Why your events never arrive Redis Memory Calculator The encoding decides, not the data Redis Key Count to Memory The fixed cost per key Redis Encoding Threshold Calculator One field more, several times the memory Redis Bitmap Memory Calculator Sized by the highest bit, not the set ones Redis HyperLogLog Calculator 12 KB whether you count a thousand or a billion Redis Cluster Sizing Only 60% of each node is usable Redis RDB and AOF Size Calculator The fork needs memory, not disk Redis Replication Bandwidth Calculator How long the backlog actually covers Redis Connection Pool Calculator More connections is not more throughput Redis Pipeline Calculator It removes round trips, not work Redis Cache Hit Rate Calculator 99% to 90% is ten times the backend load Redis Eviction Policy Simulator volatile- with no TTLs is noeviction Redis Cost Estimator Your rates, so nothing goes stale Redis Config File Generator A redis.conf with the reasons in it Redis ACL Generator A user that can do exactly one job Redis Maxmemory Config Generator The limit, and the headroom it needs Redis Persistence Config Generator How much you can afford to lose Redis Lua Script Generator Atomic, and short enough to stay that way Redis TLS Config Generator Encrypted, and the old port actually closed Redis Sentinel Config Generator Failover that can actually be authorised Redis Cluster Config Generator Three primaries, and the bus port open Redis Docker Compose Generator Local Redis that is not on the internet Redis Client Config Generator Timeouts on both sides, and a sane pool Redis MEMORY STATS Analyzer Which number actually matters Redis Bigkeys Output Analyzer Elements are not bytes Redis CLIENT LIST Analyzer Find the connection hurting you Redis LATENCY Report Analyzer An empty report may mean nothing was recorded Redis Keyspace Prefix Analyzer Which key family is growing Redis SET Command Builder A plain SET clears the TTL Redis ZRANGE Query Builder REV reverses the argument order Redis SCAN Iteration Planner COUNT is a hint, not a page size Redis Cluster Compatibility Checker Works now, breaks when you shard

Elsewhere on the site