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.

Expanding a database in Atlas Data Explorer to view collection names automatically requests statistics for all its collections. MongoDB Support reproduced this behavior and confirmed there is currently no setting to disable it.

On a high-collection-count deployment, we experienced significant application read/write latency associated with this broad statistics workload and WiredTiger schema-lock contention. Support assessed the Data Explorer statistics activity as the likely cause; the precise internal blocking mechanism remained unconfirmed.

The concern is not just slow UI loading: an ordinary browsing action can affect production database performance.

What would you like to see happen?

Describe the desired outcome or enhancement.

Provide a names-only browsing mode and allow users to search for or open a specific namespace without fetching storage statistics across the database.

Load statistics only on explicit request for a selected collection. Any optional bulk statistics operation should have bounded concurrency and cancellation.

Importantly, filtering or searching the collection list should not still trigger database-wide statistics collection in the background.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

We use Data Explorer for operational troubleshooting of multi-tenant deployments with thousands of collections and many indexes. Browsing collection names should not introduce an unexpected statistics workload that can degrade application availability or response times.

Separating namespace navigation from statistics collection would make Data Explorer safer and more usable for large production deployments.

What steps, if any, are you taking today to manage this problem?

We avoid expanding high-collection-count production databases in Data Explorer. Instead, we use listCollections with nameOnly: true through mongosh, followed by targeted $collStats requests for explicitly selected collections.

This workaround requires leaving Data Explorer and limits its usefulness for routine production troubleshooting.