Drop-index suggestions endpoint
Parent: Atlas Slow-Query Log and Performance Advisor Automation · Published reference · snapshot 2026-10-21 · skill ranked-5991fa24
↓ Facts as markdownall context files
Source-anchored research for Drop-index suggestions endpoint. Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
How it works
- The Cloud Manager v1 endpoint reference specifies GET /groups/{PROJECT-ID}/performanceAdvisor/dropIndexSuggestions. It requires clusterId or hostId as query input; hostId is required for a standalone instance when clusterId is null. The endpoint has no request body parameters. (high confidence) (verified as of 2026-10-14) [source]
Facts and statements
- The Atlas Admin API v2 operation ListDropIndexSuggestions uses GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/performanceAdvisor/dropIndexSuggestions and requires the project groupId and human-readable clusterName path parameters. (high confidence) (verified as of 2026-10-21) [source]
- The Atlas Admin API v2 reference says envelope defaults to true and models the response arrays under content. MongoDB's Go SDK reference exposes both DropIndexSuggestionsResponse and EnvelopedDropIndexSuggestionsResponse. A WithOne example shows the arrays at the top level, so callers should verify the payload shape or set envelope explicitly. (medium confidence) (verified as of 2026-10-21) [source]
- Atlas Admin API v2 returns unused, redundant, and hidden index candidates in this read-only GET response. MongoDB documents hide and drop actions separately in the UI or mongosh workflow and recommends hiding an index to evaluate it before dropping. (high confidence) [source]
- Atlas documentation defines an unused index as one that has not supported a query for at least seven days after creation or server restart. It says the Performance Advisor inspects only the 20 most active collections for unused indexes, so an empty unusedIndexes array does not establish that every collection has no unused candidate. (medium confidence) (verified as of 2026-10-20) [source]
- MongoDB defines a redundant index as a prefix of another index in the same collection. The Cloud Manager response example can include relatedIndexes for operator verification; Atlas says related indexes are not removal recommendations and advises hiding an index before dropping it. (medium confidence) [source]
- A customer-submitted MongoDB feedback entry created on 2026-10-15 reports that redundant and unused drop-index recommendations disappeared after cluster or mongod restarts and returned after workload rebuilt index usage statistics. This is one report; the API reference does not specify recommendation persistence. (low confidence) (verified as of 2026-10-15) [source]
- The versioned Atlas Admin API v2 reference lists Project Read Only as sufficient authorization for this operation; Formwise's Atlas connector catalog lists the same required role. (high confidence) (verified as of 2026-10-21) [source]
- The API v2 response categorizes candidates in unusedIndexes, hiddenIndexes, and redundantIndexes arrays; records include index name, namespace, shards, accessCount, since, and sizeBytes metadata. (high confidence) (verified as of 2026-10-21) [source]
Children
- No children recorded.