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.

The Query Insights page identifies clusters using an internal ID that is not available through the API. As a result, when a new cluster is created, we cannot programmatically construct or access the Query Insights URL for that cluster. Instead, we must manually find the required ID from the Atlas UI URL each time. This creates unnecessary operational overhead and makes automation difficult.

What would you like to see happen?

Describe the desired outcome or enhancement.

We would like MongoDB Atlas to make Query Insights accessible through a stable and externally available identifier. For example, this could be done by exposing the required cluster identifier through the API, or by allowing the Query Insights URL to use a readable identifier such as the cluster name, hostname, or cluster ID already available elsewhere in Atlas.

Why is this important to you or your team?

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

Our team manages clusters continuously, including newly created ones, and needs a reliable way to access Query Insights without manual investigation. The current URL structure prevents automation and adds repeated manual work whenever a new cluster is created. Improving this would reduce operational friction, save time, and make monitoring workflows more scalable and consistent.

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

Today, whenever a new cluster is created, we manually inspect the Atlas UI and extract the internal identifier from the Query Insights URL. We then use that value to build the necessary links or workflows. This is a manual workaround and is not scalable.