# Anti-Patterns > Depth-first rabbithole dossier for Anti-Patterns; source-anchored research pack. Parent: [MongoDB Atlas Charts](https://llms-explorer.com/tree/mongodb-atlas-charts/) · 4 facets · 11 facts · page: https://llms-explorer.com/tree/anti-patterns/ ## Measurements and reference values - 92. v1.0.0 SaaS release, 2018-12-11. D31 [H] 93. v1.4.0 (2019-06-12) added per-data-source permissions and the `Viewer` role. v1.33.1 (2022-09-12) stopped assigning individual users to `Viewer`. D31 [H] 94. v1.5.0 (2019-08-07): custom filters for Verified Signature embeds. v1.9.0 (2019-12-10): allow-listed filtering on unauthenticated charts. D31 [H] 95. v1.6.0 (2019-09-03): data-source pipelines (now charts views). v1.19.0 (2020-10-13): lookup fields. D31 [H] 96. SDK preview v1.10.0 (2020-02-05). SDK GA with Custom JWT/Realm/Google auth v1.13.0 (2020-04-30). JWK/JWKS v1.27.0 (2021-09-13). D31 — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/anti-patterns-8d2be39d61/rabbithole-synthesis.md#3-history-how-the-guardrails-appeared` ## Problems, failure modes and limitations - 1. Charts builds one pipeline per chart in a fixed order: charts views → embedding pre-filters → dashboard filters → chart query → lookup fields → calculated fields → embedding filters (including injected filters) → chart filters → encoded fields → sorting → max-document limit. D1 [M,P] MDB 2. Charts skips any segment the author did not configure. D1 [M] MDB 3. "View Aggregation Pipeline" in the Chart Builder shows the generated pipeline. It is the main diagnostic. D1, F1 [M,E,P] MDB 4. A staff member gives a second debugging step: read the Atlas profiler (`system.profile`) to see the queries — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/anti-patterns-8d2be39d61/rabbithole-synthesis.md#1-the-mechanism-the-anti-patterns-act-on` - 19. MongoDB discontinued on-premises Charts in September 2021. A MongoDB staff member wrote on 2022-02-01: "The on-prem version was discontinued last September. We did include a notice about this for around a year before support ended." https://www.mongodb.com/community/forums/t/is-mongodb-charts-discontinued/144944 20. Search snippets give the exact on-prem end-of-life date as 2021-09-01. The primary notice host (mongosilverback.net) did not resolve, and the MongoDB lifecycle page has no Charts row, so this exact day is only partly confirmed. https://www.mongodb.com/legal/support-policy/lifec — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/anti-patterns-8d2be39d61/reports/history.md#b-platform-history-that-created-anti-patterns` - 24. Using unauthenticated embedding for sensitive data is an anti-pattern. MongoDB says unauthenticated access "is less secure and should only be used for charts that display non-sensitive data." This is from a search summary of the Manage Data Sources page. https://docs.mongodb.com/charts/saas/manage-data-sources 25. Allowing filtering on fields that reveal sensitive data is an anti-pattern. By default, embedded charts allow no filter fields until the author adds at least one. https://www.mongodb.com/docs/charts/filter-embedded-charts/ ; https://www.mongodb.com/docs/charts/embed-chart-anon-au — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/anti-patterns-8d2be39d61/reports/history.md#c-current-documented-anti-patterns` - 1. Charts builds one aggregation pipeline per chart. The segment order is: charts views, embedding pre-filters, dashboard filters, chart query, lookup fields, calculated fields, embedding filters (including injected filters), chart filters, encoded fields, sorting, then the maximum document limit. https://www.mongodb.com/docs/charts/aggregation-pipeline-generation.md 2. Charts skips any segment the author did not configure. https://www.mongodb.com/docs/charts/aggregation-pipeline-generation.md 3. Authors can inspect the generated pipeline with "View Aggregation Pipeline" in the Chart Builder. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/anti-patterns-8d2be39d61/reports/mechanism.md#a-mechanism-the-anti-patterns-act-on` - **Scope.** In: the mechanisms that make a Charts usage pattern harmful, their limits, history, failure modes and disagreements. Out: siblings (SDK/REST surface, access control, cost model, chart-type catalogue, auth providers), general MongoDB schema anti-patterns and general query tuning. The parent's heatmap row and `tenantId: 'acme'` snippet are not counted as evidence. Claims that refine them are listed under Deltas. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/anti-patterns-8d2be39d61/rabbithole-synthesis.md` - Framing caveat: MongoDB does not publish a page called "Charts anti-patterns." The Charts docs navigation has no such section (https://www.mongodb.com/docs/charts/). The concept is a synthesis of warnings that are spread across individual docs pages. Each claim below cites the page where the warning appears. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/anti-patterns-8d2be39d61/reports/history.md#scope` ## Comparisons and alternatives - In scope: the operational anti-patterns in Atlas Charts, meaning query shape, pipeline ordering, indexing, result-size limits, caching and refresh, workload placement, embedding authentication, and filter security. For each one the report covers the trade-off, how to check for it, and what it means in practice. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/anti-patterns-8d2be39d61/reports/practice.md#scope` ## Facts and statements - Out of scope: sibling concepts (the cost model, analytics-node configuration, the Embedding SDK API as a whole, chart types), general MongoDB schema anti-patterns (Atlas Performance Advisor), and general aggregation tuning. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/anti-patterns-8d2be39d61/reports/history.md#scope` - **Out of scope:** general MongoDB schema anti-patterns, the SDK and REST API surface, the access-control model and the cost model as topics in their own right. Those are sibling frontier items. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/anti-patterns-8d2be39d61/reports/mechanism.md#scope` - **Inherited parent facts:** none were reused as findings. The parent only lists "anti-patterns" as a section heading. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/anti-patterns-8d2be39d61/reports/mechanism.md#scope`