Solution skill
Atlas: use the Real-Time Performance Panel when the cluster feels slow
Complete solution
The RTPP shows live operations with scanned-vs-returned ratios. This is the fastest way to find what is hurting right now. Not for different error messages.
TL;DR: The RTPP shows live operations with scanned-vs-returned ratios. This is the fastest way to find what is hurting right now. Confirm Pick the top operation by total time. Copy its shape and run explain("executionStats") to confirm the plan (COLLSCAN, in-memory sort, or a fine IXSCAN that is just called too often).
The fix
- Operations by namespace: which collection is hot.
- Operation execution time: what is actually slow vs just frequent.
- Scanned vs returned: the ratio that fingers missing indexes.
- Bad plan: add the index (see the COLLSCAN and query-targeting skills).
- Good plan, too frequent: cache it, batch it, or move it off the hot path.
- One huge operation: kill it if it is a runaway (with the right role), then fix the query.
- You are seeing this exact error message; match the block above, not just part of it.
- The failing call matches the scenario in the title: Atlas.
- You want the fastest verified fix before digging through logs.
- Your error text differs from the block above; close cousins often have different causes.
- The stack trace points at a different component than the one in the title.
- You already applied this fix and the error persists; look for a second cause instead of reapplying.
When to use this
- This covers exactly what the title says: Atlas.
- You are setting this up for the first time, or auditing an existing setup.
- You want the key gotchas in one place before you start.
When not to use this
- You are doing a different workflow with Atlas; these steps are specific to the title above.
- You need the full reference docs; this is the short path, not the manual.
Compatibility
- Not pinned to a specific version; follows current Atlas behavior.
Evidence
Real-Time Performance Panel capabilities (live operations, execution times, scanned-vs-returned ratio) per the Atlas slow-query analysis docs and https://www.mongodb.com/docs/atlas/performance-advisor/, verified 2026-09-26.
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_saovxCbyzL141EVt3-wOBA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Atlas: use the Real-Time Performance Panel when the cluster feels slow <span>— Vectle</span></a>