What is actually in there?

RedisDataStudio » Use cases » See what is in Redis

Download RedisDataStudio Free Trial »     Buy RedisDataStudio Now »

The situation

Something in Redis is wrong - a session is not found, a cache returns stale data, a counter is out of step - and the answer is in a key somewhere. What you have is a shell, redis-cli, and a memory of the command for listing keys but not for reading the value of a hash the way you need to see it.

Reading raw key dumps also hides the two things that usually explain the problem: which type the value really has, and when it expires.

What you do

  1. Connect to the server: host, port, password. SSL and password authentication are supported, and several Redis servers can be kept in the same list.
  2. Browse the keys, and open one to see its value in the shape its type deserves - a string, a hash as a field/value table, a list, a set, a sorted set, or JSON.
  3. Read the properties that matter for debugging: the type, the size and the TTL.
  4. Nothing is written unless you decide to write - opening a key is a read.

Browsing and reading Redis keys in RedisDataStudio

Everything runs from your machine directly to the Redis server you name: no agent, no cloud service, and no copy of the data anywhere else. On a production server, that means looking is safe and reading is exactly a read.

What it will not do

Related

Changing what you find: fix one wrong value. Loading a whole namespace: from CSV or Excel. Getting a copy out for analysis: export a slice of Redis. The modes: edit key data, one key in and out, a whole namespace.