Redis Officially Launches RedisInsight: A Stunning GUI with Powerful Features
RedisInsight is a visual GUI for Redis that uniquely supports Redis Cluster, offers SSL/TLS connections, memory analysis and an integrated CLI; the article walks through downloading the package, configuring environment variables, starting the service on Linux, deploying it on Kubernetes with a YAML manifest, and using the UI to monitor and operate Redis instances.
RedisInsight Overview
RedisInsight is an intuitive, high‑performance GUI management tool for Redis. It monitors memory usage, connection count, hit rate and uptime, provides an integrated CLI, supports Redis modules, and is the only GUI that can manage a Redis Cluster.
Key Features
Unique support for Redis Cluster
Browser‑based key search, view and edit
SSL/TLS connection support and built‑in memory analysis
1. Physical Installation on Linux
Download the RedisInsight package and place it in a dedicated directory.
[root@Redis ~]# ls
anaconda-ks.cfg redisinsight-linux64-1.11.0
[root@Redis ~]# mkdir /usr/local/redisinsight
[root@Redis ~]# mv redisinsight-linux64-1.11.0 /usr/local/redisinsight/redisinsight-1.11.0
[root@Redis ~]# chmod +x /usr/local/redisinsight/redisinsight-1.11.0Configure environment variables for host, data directory, log directory and listening port.
# echo "export REDISINSIGHT_HOST=192.168.1.1" >> ~/.bash_profile
# echo "export REDISINSIGHT_HOST_DIR=/usr/local/redisinsight/.redisinsight" >> ~/.bash_profile
# source ~/.bash_profileVariable details: REDISINSIGHT_PORT: default 8001 REDISINSIGHT_HOST: default 0.0.0.0 LOG_DIR: defaults to
REDISINSIGHT_HOST_DIR REDISINSIGHT_HOST_DIR: default ~/.redisinsight Start the service in the background.
# nohup /usr/local/redisinsight/redisinsight-linux64-1.4.0 &
# ps aux | grep redis # verify the process2. Kubernetes Deployment
Create a redisinsight.yaml manifest that defines a Service (NodePort 31888 → targetPort 8001) and a Deployment using the official Docker image.
apiVersion: v1
kind: Service
metadata:
name: redisinsight-service
spec:
type: NodePort
ports:
- port: 80
targetPort: 8001
nodePort: 31888
selector:
app: redisinsight
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: redisinsight
spec:
replicas: 1
selector:
matchLabels:
app: redisinsight
template:
metadata:
labels:
app: redisinsight
spec:
containers:
- name: redisinsight
image: redislabs/redisinsight:1.7.0
imagePullPolicy: IfNotPresent
volumeMounts:
- name: db
mountPath: /db
ports:
- containerPort: 8001
protocol: TCP
volumes:
- name: db
emptyDir: {}Deploy with:
# kubectl apply -f redisinsight.yaml3. Basic Usage
Install Redis (example uses 6.2.6) if not already present, then adjust the configuration to bind the desired IP, disable protected mode, enable daemonize, and set a password.
# wget https://download.redis.io/releases/redis-6.2.6.tar.gz
# tar zxf redis-6.2.6.tar.gz
# cd redis-6.2.6
# make PREFIX=/usr/local/redis install
# sed -i '/^bind 127.0.0.1/s/127.0.0.1/192.168.1.1/g' redis.conf
# sed -i '/protected-mode/s/yes/no/g' redis.conf
# sed -i '/daemonize/s/no/yes/g' redis.conf
# sed -i '/requirepass/s/foobared/123123/g' redis.conf
# cp redis.conf /usr/local/redis/
# /usr/local/redis/bin/redis-server /usr/local/redis/redis.confAccess the RedisInsight UI using the configured IP and port (default 8001). The UI displays Redis statistics, allows key operations, and provides a memory‑analysis view.
Through the interface you can:
View real‑time memory, connections, hit rate and uptime
Execute CLI commands directly in the browser
Perform key CRUD operations via a searchable grid
Run built‑in memory analysis to identify large keys and fragmentation
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Java Architect Handbook
Focused on Java interview questions and practical article sharing, covering algorithms, databases, Spring Boot, microservices, high concurrency, JVM, Docker containers, and ELK-related knowledge. Looking forward to progressing together with you.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
