Skip to content
Documentation
Development documentation
This describes Keydra as it is being built and is not a released version. What it documents can change before a release.

The key browser

Keys stream in as the server scans them, grouped into a namespace tree and filtered by glob and type. Never KEYS, always a cursor.

How the key browser reads a keyspace#

Keydra never issues KEYS. Enumeration is always a cursor-based SCAN, and the results are streamed to the browser as the server produces them — so the first keys render while the walk is still running, and a keyspace of any size is walked rather than held.

The key browser, with the namespace tree on the left and keys with their type and TTL on the right

That is why the page says {count} keys so far while it works, and why Rescan rather than Refresh is the word on the button: there is no cached list to refresh.

Namespace tree

Keys are grouped on the : delimiter into a tree, loaded lazily. A branch with more children than the tree will draw says and {count} more — use the search box.

Search

A glob pattern, passed to the server as SCAN’s `MATCH. The placeholder shows the shape: user:*.

Type filter

Narrows to one of the server’s types.

Limit

The page holds as many keys as it safely can. When it reaches that, it says Limit reached and explains that narrowing the filter shows different ones. It does not silently stop.

Each row carries the key’s type and its TTL, read in the same pass.

Browsing keys#

Prerequisites

  • You hold keys:read on the target.

Procedure

  1. Go to Connections and open the target, or use Keys in the navigation while a target is open.

  2. Optionally narrow what is scanned:

    • Type a glob into Search keys — for example user:*.

    • Choose a type from All types.

    • Click a branch in the namespace tree on the left.

  3. Click a key to open its value.

Verification

The count in the toolbar rises while the scan runs and settles when it finishes. A key’s row shows its type and, where it has one, its TTL; keys without one read No expiry.

Next steps

Deleting, renaming and expiring keys#

Prerequisites

  • keys:delete to delete, keys:write to rename, duplicate or change a TTL.

Procedure

To delete:

  1. Select one or more rows, or open a row’s actions menu.

  2. Click Delete, or Delete {count} for a selection.

  3. The dialog names what will go and says it cannot be undone. Confirm.

To rename:

  1. Open the row’s actions menu and choose Rename.

  2. Give the New name. If a key of that name exists, the dialog refuses and offers Overwrite the destination if it already exists.

  3. Confirm.

To duplicate:

  1. Open the row’s actions menu and choose Duplicate.

  2. Give the New name, with the same overwrite option.

To set or clear an expiry:

  1. Open the row’s actions menu and choose Set TTL.

  2. Enter Seconds until expiry, or tick Remove the expiry instead.

  3. Confirm.

Verification

The list updates without a rescan: the change is broadcast over the notification hub, so every browser looking at that target sees it — including a colleague’s.

Edit this page