Skip to content

How to see all keys? #1469

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nickworks opened this issue Apr 25, 2025 · 2 comments
Closed

How to see all keys? #1469

nickworks opened this issue Apr 25, 2025 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@nickworks
Copy link

How do you see all keys in redis insight?

Typing an asterisk in the search box does not work -- it only matches keys in the current namespace. The little namespace switcher works at the top, but you have to know the name of the namespace to switch to it.

Is there anyway to see all keys?? Or a way to see all namespaces?

Thanks

@dwdougherty
Copy link
Collaborator

dwdougherty commented Apr 25, 2025

Hi @nickworks. Thank you for your question. I assume that by namespace, you mean some kind of consistent prefix, for example foo:1, foo:2, foo:3. In the browser, you can use either foo:* or just *, or you can just use the KEYS * command in the CLI. Both these options are shown in the attached image.

Image

@dwdougherty dwdougherty self-assigned this Apr 25, 2025
@dwdougherty dwdougherty added the question Further information is requested label Apr 25, 2025
@nickworks
Copy link
Author

Hello David,

I think I was erroneously referring the isolated keyspaces ("db0", "db1") as "namespaces". There was a bit of disconnect for me coming from the Laravel documentation, but I think I have it figured out now. Laravel's cache.php config file allows me to associate specific Redis keyspaces with certain Laravel features, and I was confused by there being two of these set up.

Thank you for the response!
Nick

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants