# Namespace Insights > Source-anchored research for Namespace Insights. Run status: COMPLETED. Parent: [MongoDB Query Optimization Tooling: Compass Explain, Atlas Query Insights and Performance Advisor](https://llms-explorer.com/tree/mongodb-query-optimization-tooling-compass-explain-atlas-query-insights-and-performance-advisor/) · 4 facets · 16 facts · page: https://llms-explorer.com/tree/namespace-insights/ ## Structure and components - The page contains two charts and a table. Users can chart at most five namespaces and pin at most five; the default selection favors pinned namespaces and namespaces with the highest total latency. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/namespace-insights.md) - Microsoft’s Azure deployment architecture lists Namespace Insights as an extension to its monitoring solution, alongside a separate Azure Functions component that collects Atlas API metrics. This listing does not establish that Namespace Insights charts are directly exported by that component. (low confidence) — [source](https://learn.microsoft.com/en-us/azure/architecture/databases/architecture/mongodb-atlas-baseline) ## How it works - Namespaces can enter or leave the automatically monitored top list as the time window changes. Atlas can interpolate missing data when host metrics exist at both ends, and uses dotted lines for gaps; a continuous-looking trend need not represent continuous observation. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/namespace-insights.md) ## Problems, failure modes and limitations - A local-shard $lookup can increment foreign-collection latency and operation counts without a foreign-collection slow-query log. SERVER-98528 documents this mismatch and includes a reproducer. (high confidence) (verified as of 2026-10-23) — [source](https://www.mongodb.com/docs/atlas/namespace-insights.md) - When the chart data limit is reached, reduce the selected time window or number of hosts. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/namespace-insights.md) ## Facts and statements - Namespace Insights displays collection-level latency and operation counts, with reads, writes, and commands selectable separately. (high confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/namespace-insights.md) - The documented feature requires an M10+ cluster; time series collections are unsupported, and collections using Queryable Encryption are redacted from this view. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/namespace-insights.md) - Filters support node, primary or secondary state, and shard, with a custom interval within the last seven days. Analytics nodes are included in the secondary-state filter. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/namespace-insights.md) - Available chart metrics include total latency, average latency, P50, P95, P99, and operation count; total latency and operation count are rates. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/namespace-insights.md) - Average latency uses changes in cumulative server duration and operation count measured ten minutes apart. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/namespace-insights.md) - On October 18, 2024, Frank Sun replied in the MongoDB Community forum that Namespace Insights does not show documents scanned or returned; MongoDB's Query Insights launch post identifies him as a Senior Product Manager, and the current documented metric list also omits those measures. (medium confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/namespace-insights.md) - Namespace Insights provides collection-level query latency monitoring in MongoDB Atlas, helping identify which namespaces warrant further performance investigation. (medium confidence) — [source](https://www.mongodb.com/docs/atlas/namespace-insights.md) - The documented Atlas interface places Namespace Insights under the cluster Query Insights page, on its Namespace tab. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/namespace-insights.md) - Metrics include total latency, average latency, P50, P95, P99, and operation count. Users can select reads, writes, commands, or all operation types. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/namespace-insights.md) - Total latency is combined server operation duration divided by the collection interval in seconds; operation count is also a rate. Average latency uses differences in operation-time and operation-count counters over a ten-minute interval. These measures should not be read as interchangeable per-request durations. (low confidence) — [source](https://www.mongodb.com/docs/atlas/namespace-insights.md) - Netdata’s original monitoring-tool comparison recognizes Namespace Insights as providing collection-level query latency, while evaluating Atlas monitoring as scoped to Atlas-hosted clusters. This is a competitor assessment, not independent benchmark evidence for the accuracy of latency statistics. (low confidence) — [source](https://www.netdata.cloud/resources/best-mongodb-monitoring-tools/)