redis / redis/RedisInsight

[Feature Request]: Logical Database Aliases and Metadata (Description, Tags)

Open
#6,437 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature
Dominant language
TypeScript
Stars
8.8k
Forks
491
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Problem

Logical databases (db0, db1, ...) are only shown by numeric index. In real projects each index serves a different purpose (sessions, cache, queues, etc.), but there's no way to tell which is which without digging through docs or code.

Proposal

Let users assign an alias, short description, and optional tags to each logical database (via UI and/or a shareable config file, e.g. redis-db-map.json).

Instead of manually typing/selecting the DB by index, show a dropdown/list of logical databases (by alias) when switching databases.

Example
DB Alias Description Tags
db0 Sessions User sessions & tokens auth, session
db1 Cache Application cache cache
db2 Queues Background job queues queue, jobs
db3 Rate Limit Request rate limiting rate-limit

Benefits

  • Faster onboarding, fewer mistakes (wrong DB selected)
  • Self-documenting database browser
  • Config file can be shared/versioned across the team
Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the logical database selector and any existing configuration handling, then clarify whether the scope includes UI metadata, a shareable config file, or both; done means aliases, descriptions, tags, and alias-based database selection have an agreed design and coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
redis, typescript
Domain
database, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.