I have set up the basic sentinel configuration 3 nodes and 3 sentinels. I also have installed redis insight on my computer to access those nodes. When I consult the client list, only sentinels have a declared client name. Is there a way to define client names for nodes and redisinsight connections in configuration files or environment variables?
Comment From: yossigo
@mmorel-35 clients can assign names to their connections using the CLIENT SETNAME command. Sentinel uses this capability, but Redis as a replica, and apparently RedisInsight don't. I'm not sure about RedisInsight, but for Redis there's no way to configure that.
Comment From: mmorel-35
Thanks for the reply @yossigo . Would it be possible to make it a feature request for the replicas and redisinsight to have a default client name defined when they create a connection ? This way, any supervisor wouldn't need to ask himself if the connection is legitimate or not.
Comment From: yossigo
@mmorel-35 What do you consider a legitimate connection? Keep in mind that any "illegitimate" client can do CLIENT LIST, observe the names of the other connections and then CLIENT SETNAME to mimick them.
Comment From: mmorel-35
I see, anyone can set any client name. When I first read list of clients I couldn't determine who was connected. With the ips you can guess. I didn't setup acls at that time so anyone who knew redis existed here could access it. What I'd like to to see on client list is who is connected with a more readable name than the ip and port
Comment From: yossigo
@mmorel-35 You should use ACLs for that. You can create individual users with their own passwords, and once they're connected and authenticated their name will show up in the user= field of CLIENT LIST.
Comment From: oranagra
question was answered. feel free to reopen or respond if needed.