Muokkaa

Jaa


Use the Redis command-line tool with Azure Managed Redis (preview)

Use the redis-cli command-line tool to interact with an Azure Managed Redis (preview) as a client. Use this tool to directly interact with your Azure Managed Redis instance and for debugging and troubleshooting.

Install redis-cli

The redis-cli tool is installed automatically with the Redis package, which is available for multiple operating systems. See the open source install Redis guide for the most detailed documentation on your preferred operating system.

Linux

The redis-cli runs natively on Linux, and most distributions include a Redis package that contains the redis-cli tool. On Ubuntu, for instance, you install the Redis package with the following commands:

sudo apt-get update
sudo apt-get install redis

Windows

The best way to use redis-cli on a Windows computer is to install the Windows Subsystem for Linux (WSL). The Linux subsystem allows you to run linux tools directly on Windows. To install WSL, follow the WSL installation instructions.

Once WSL is installed, you can install redis-cli using whatever package management is available in the Linux distro you chose for WSL.

Gather cache access information

You can gather the information needed to access the cache using these methods:

In this section, you retrieve the keys from the Azure portal.

Retrieve host name, ports, and access keys from the Azure portal

To connect your Azure Cache for Redis server, the cache client needs the host name, ports, and a key for the cache. Some clients might refer to these items by slightly different names. You can get the host name, ports, and keys from the Azure portal.

  • To get the access keys, select Authentication from the Resource menu. Then, select the Access keys tab.

    Screenshot showing Azure Cache for Redis access keys.

  • To get the host name and ports for your cache, select Overview from the Resource menu. The host name is of the form <DNS name>.redis.cache.windows.net.

    Screenshot showing Azure Cache for Redis properties.

Connect using redis-cli

Open up a shell or terminal on a computer with the Redis package installed. If using WSL, you can use the Windows Terminal to open a Linux command line. Before connecting with redis-cli, check:

  1. Whether TLS access is needed - By default, Azure Managed Redis instances use TLS encryption for connections. Whenever TLS is used on the server side, TLS on redis-cli must be enabled using the --tls option.
  2. The port used - all Azure Managed Redis instances use port 10000. Note that this is different than the default for the Redis community edition, which is 6379.
  3. Whether the cache instance uses the OSS cluster policy - If you're using the OSS cluster policy, add the -coption to ensure all shards can be accessed.

Examples

  1. Connect to an Azure Managed Redis instance using Enterprise cluster policy with TLS:

    redis-cli -p 10000 -h {yourcachename}.{region}.redis.azure.net -a YourAccessKey --tls
    
  2. Connect to an Azure Managed Redis instance using OSS cluster policy and TLS:

    redis-cli -p 10000 -h {yourcachename}.{region}.redis.azure.net -a YourAccessKey --tls -c
    

Testing the connection

Once the connection is established, you can issue commands to your Azure Managed Redis instance. One easy way to test the connection is to use the PING command. This command returns PONG in the console.

yourcachename.region.redis.azure.net:10000> PING
PONG

You can also run commands like SET and GET:

yourcachename.region.redis.azure.net:10000> SET hello world
OK
yourcachename.region.redis.azure.net:10000> GET hello
"world"

You're now connected to your Azure Managed Redis instance using the redis-cli.

redis-cli alternatives

While the redis-cli is a useful tool, you can connect to your cache in other ways for troubleshooting or testing:

  • RedisInsight is a rich open source graphical tool for issuing Redis commands and viewing the contents of a Redis instance. It works with Azure Managed Redis and is supported on Linux, Windows, and macOS.

Get started by creating a new Azure Managed Redis Instance instance.