Skip to main content
0 reactions

Valkey Tutorial — Part 3: Valkey Admin for Beginners

Featured card labelled Valkey Tutorial Part 3, titled Valkey Admin for Beginners, with an app window showing four cards (infinity, 1.42 MB, 177 and 100%), a rising chart and the words Keys, Commands, Dashboard.
Valkey Tutorial, Part 3.

In Part 2 you worked with Valkey® from the terminal. Valkey Admin, the Valkey project’s own app, shows the same data in a window: your keys as a tree with their types and sizes, a box for commands, and a Dashboard of the server’s health.

In this part you connect Valkey Admin to your Valkey, save the Bookshop’s first book with commands, find it in the Key Browser, change its price, and see the activity on the Dashboard.

This is Part 3 of the Valkey Tutorial. The parts in Module A, Start Here:

All parts of the Valkey Tutorial

Module A: Start Here

Module B: Data Types

  • Part 4: Strings and Counters
  • Part 5: Key Expiration and TTL
  • Part 6: Hashes
  • Part 7: Lists
  • Part 8: Sets
  • Part 9: Sorted Sets and Leaderboards
  • Part 10: Bitmaps, Bitfields and HyperLogLog
  • Part 11: Geospatial Indexes
  • Part 12: Streams

Module C: Keys, Transactions and Scripting

  • Part 13: Managing Keys and Databases
  • Part 14: Transactions with MULTI, EXEC and WATCH
  • Part 15: Lua Scripting
  • Part 16: Functions
  • Part 17: Pub/Sub and Keyspace Notifications
  • Part 18: Common Patterns: Locks, Rate Limits and Queues

Module D: Configure and Persist

  • Part 19: Configuration and Running as a Service
  • Part 20: Persistence: RDB Snapshots and AOF
  • Part 21: Backup and Restore
  • Part 22: Memory and Eviction

Module E: Monitor and Tune

  • Part 23: Monitoring Valkey
  • Part 24: Benchmark with valkey-benchmark

Module F: Security

  • Part 25: Passwords and ACL Users
  • Part 26: TLS Encryption
  • Part 27: Remote Access on Ubuntu, Safely

Module G: High Availability and Scale

  • Part 28: Replication
  • Part 29: Sentinel: Automatic Failover
  • Part 30: Valkey Cluster
  • Part 31: Cluster Operations

Module H: Docker and Modules

  • Part 32: Run Valkey in Docker and Docker Compose
  • Part 33: JSON Documents
  • Part 34: Bloom Filters
  • Part 35: Search and Vector Search

Module I: Valkey for Developers

  • Part 36: Connect from C# .NET with Valkey GLIDE
  • Part 37: Caching in ASP.NET Core with Valkey
  • Part 38: Aspire with Valkey
  • Part 39: Connect from Python with Valkey GLIDE
  • Part 40: Connect from Node.js with Valkey GLIDE

Module J: Production and Cloud

  • Part 41: Free Hosted Valkey on Aiven
  • Part 42: Production Checklist on Ubuntu
  • Part 43: Migrate from Redis to Valkey
  • Part 44: Upgrade Valkey
  • Part 45: Final Project, Cheat Sheet and What to Learn Next

Cost: free. Everything in this part runs on your own computer.

Note: Every command and screen on this page is real, run on Valkey 9.1 with Valkey Admin 1.3.0 on macOS.

Prerequisites

  • Valkey running on your computer, as at the end of Part 2.

Step 1: Open Valkey Admin and Connect

Open Valkey Admin: the desktop app (How to Install Valkey Admin on macOS) or the web version at http://localhost:8091 (How to Run Valkey Admin in Docker).

  1. Click + Add Connection.
  2. In Alias, type a name you’ll recognise, such as Local Valkey.
  3. In Host, type localhost in the desktop app, or host.docker.internal in the Docker version. Leave Port at 6379.
  4. Untick Use TLS. It’s ticked by default, but the Valkey on your computer doesn’t use TLS.
  5. Click Connect.
The Valkey Admin Add Connection form with Endpoint Type Node, Alias Local Valkey, Host host.docker.internal, Port 6379, empty Username and Password, Database 0, Use TLS unticked and a warning that the connection will not be encrypted.
In Docker, the host is host.docker.internal, with Use TLS unticked.

Valkey Admin opens the Dashboard of your server. The four cards show the memory limit (∞ means none is set), the memory in use, the number of commands the server has processed and its hit ratio, a dash until something has been read:

The Valkey Admin Dashboard for instance host-docker-internal-6379-db0, with cards showing Total Memory infinity, Used Memory 1.23 MB, Operations 32 and a dash for Hit Ratio.
Connected: the Dashboard of the local Valkey.

Step 2: Save a Book with Send Command

Click Send Command in the sidebar. It works like valkey-cli: type a command in the box at the bottom and click Send. Send these three, one at a time:

Send CommandPlain text
SET book:4:title "Salt and Starlight"
Send CommandPlain text
SET book:4:author "Nadia Quill"
Send CommandPlain text
SET book:4:price 9.99

Each one replies:

ResponsePlain text
OK

Then read the price back:

Send CommandPlain text
GET book:4:price
ResponsePlain text
9.99

The reply appears under Response, with how long the round trip to the server took. Every command you send goes into History on the right, where you can copy it or run it again.

Valkey Admin Send Command with the reply 9.99 and its round-trip time under Response, and a History list of SET book:4:title, SET book:4:author, SET book:4:price 9.99 and GET book:4:price with their times.
GET book:4:price replies 9.99, and every command goes into History.

Step 3: Find Your Keys in the Key Browser

Click Key Browser. It groups keys by the colons in their names, the object:id:field habit from Part 2, so book:4:title, book:4:author and book:4:price sit under book › 4. Click the arrows to open the groups. Each key shows its type, its size and whether it expires.

The Valkey Admin Key Browser tree with the group book (3), its subgroup 4 (3), and the keys title, author and price, each marked STRING with its size and No expiry.
The Key Browser groups the three keys under book › 4.

Click price. Its details open on the right: the key’s name, No expiry, its type and size, and its value, 9.99.

The Valkey Admin Key Browser with the price key selected and its details on the right: book:4:price, No expiry, string, 32 B, a delete icon, and the value 9.99 with an edit pencil.
Click a key to see its expiry, type, size and value.

Step 4: Change a Value

Click the pencil icon next to Value, change 9.99 to 8.99, and click the tick to save.

The details of book:4:price in the Valkey Admin Key Browser after editing, with the value now 8.99.
After saving, book:4:price holds 8.99.

The change is in Valkey itself. Back in Send Command, the same GET now replies with the new price:

Send CommandPlain text
GET book:4:price
ResponsePlain text
8.99

Step 5: Read the Dashboard

Click Dashboard. Operations has grown with your commands, and Hit Ratio shows 100.00%: every read so far found its key.

Valkey Admin Dashboard cards showing Total Memory infinity, Used Memory 1.42 MB, Operations 177 and Hit Ratio 100.00 percent.
After the commands: 177 operations and a 100% hit ratio.

Lower down, charts follow the server over time. Open the Keys Count chart with its expand icon to see the moment your keys arrived:

The Keys Count chart in Valkey Admin set to the last 1 hour, with data available since 19 Nov 08:53, rising from 1 key to 3 keys at 08:53:48.
Keys Count shows when the three book keys arrived.

Clean Up

Delete the three keys in Send Command:

Send CommandPlain text
DEL book:4:title book:4:author book:4:price
ResponsePlain text
3

The reply is the number of keys deleted, and the Key Browser shows 0 keys again.

Common Mistakes

MistakeWhat happensDo this instead
Typing localhost as the Host in the Docker versionValkey Admin looks for Valkey inside its own containerType host.docker.internal
Sending SELECT 1 to switch databasesSend Command blocks it, because SELECT would change the database of the connection Valkey Admin sharesSet Database when you add the connection
Sending KEYS *Valkey Admin asks you to confirm, because KEYS can block a server with many keysUse SCAN, as in Valkey KEYS vs SCAN

FAQ

Can I use Valkey Admin with a Valkey server on another computer?

Yes. Type that server’s host and port when you add the connection. Keep Use TLS ticked if the server uses TLS, and fill in Username and Password if it asks for them.

Does Valkey Admin replace valkey-cli?

No. Both talk to the same server. The rest of this tutorial types commands in valkey-cli and uses Valkey Admin where seeing the result helps.

Conclusion

Valkey Admin gives you a window onto Valkey: connect once, run commands in Send Command, see and edit keys in the Key Browser, and watch the server on the Dashboard.

← Previous: Part 2: Your First Valkey Commands with valkey-cli

Coming next: Part 4: Strings and Counters.

Additional Resources

Valkey® is a registered trademark of LF Projects, LLC. Redis® is a registered trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd. Other names mentioned are trademarks of their respective owners. JD Bots isn’t affiliated with the Valkey project, LF Projects or Redis Ltd., and isn’t endorsed, supported or certified by them.

0 comments