Welcome to the new MongoDB Feedback Portal!
{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.
We’ve upgraded our feedback system to better capture, track, and act on your feedback. Here’s what you need to know:
|
What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. |
There is no easy way to check all the indexes that are created in a project. Besides, you cannot easily create, edit or remove them from the UI. |
|
What would you like to see happen? Describe the desired outcome or enhancement. |
A new section that shows all the indexes you have created in a project, with options to filter by cluster, database and collection |
|
Why is this important to you or your team? Explain how the request adds value or solves a business need. |
If we want the full list of indexes, we need to run a script to get it. And if we want to check a specific database, we need to access to each collection and then check the indexes for that collection. |
What steps, if any, are you taking today to manage this problem? |
Hi @Guest , Thank you for reaching out and giving your feedback around the Index management.
You are correct that there is no dedicated index management tab in the main Atlas UI, but this is also intentional as index information has potentially sensitive cluster data in the index itself like field names. In order to ensure the proper data privacy for different users, we actually have this information in the Data Explorer tool within the Atlas UI. There's even a specific index tab in Data Explorer that is already there today that would be the best place for you to see indexes for a given collection. Your Atlas user will need the Data Access Admin role in order to create/edit/remove indexes, as pre your requests.
Data Explorer → Indexes tab is the canonical place to see and directly manage non-search indexes: create (single/compound/text/2dsphere/wildcard), configure TTL/partial/sparse/collation, hide/unhide, drop, and inspect primary-node usage.
Performance Advisor can also give relevant information for indexes:
For adding indexes: slow-query analysis → ranked suggestions → in the UI you can use “Create Suggested Index” flow (with options and rolling builds).
For removing indexes: unused/redundant/hidden detection → “Drop Index” recommendations linked back into the Indexes tab.
In case you are using MongoDB Search and/or Vector Search indexes have their own full lifecycle UIs under Search & Vector Search, separate from the index management above, but still allows you to create, inspect, update, delete Search and Vector Search indexes from the UI.
Hopefully this helps guide you to the best place to look at these in the UI. Data Explorer is the area that we believe it is best at this time to for index management while ensuring more specific and/or sensitive cluster data is only shown to the correct users. We do not have any plans on our roadmap at this time to create a specific page just for Index management outside of Data Explorer in MongoDB Atlas.