Documentation
8 results found
-
Offline Documentation
Provide PDF versions of documentation, for situations where we don't have consistent network connectivity or to keep a version of the documentation for old versions of the server
8 votes -
Provide Database Tools version vs Ops Manager version Compatibility table or matrix
Be able to quickly identify the Database Tools version for a specific Ops Manager release version via a table or matrix for installation, rather than reading through various releases.
5 votes -
Rename a MongoDB Replica Set is not useful if you're working MongoDB Ops Manager
Documentation for renaming a MongoDB Replica Set is not useful when you use MongoDB Ops Manager. You should consider refactoring your documentation since renaming a MongoDB Replica Set which is managed by MongoDB Ops Manager does not work.
I had to rename a MongoDB Replica Set which is managed by MongoDB Ops Manager. As stated in your documentation, I suspended the MongoDB Replica Set in question from being managed by MongoDB Ops Manager and did all the changes you list in your documentation. Everything worked fine until I wanted to have the MongoDB Automation Agent restart the MongoDB Replica Set.…
3 votes -
List of log messages and logging levels
It would be nice if there was a list of log messages with respective logging levels within each logging component. Then we could conclusively determine what log level we want to use, without requiring us to determine the same thing experimentally - which is time consuming. Please add this!
2 votes -
Enhance MongoDB Documentation on Schema Validation Impact on Write Operations
MongoDB documentation should clearly explain how schema validation affects write operations, including bulkWrite, insertOne, insertMany, updateOne, and updateMany. Key improvements:
Performance Impact – Detail validation overhead on write latency.
Validation Scope – Specify when validation is triggered during writes.This will help developers optimize write operations while using schema validation effectively.
Current solution:
Schema validation requires MongoDB to check documents before committing writes—this inherently introduces some processing overhead.
Bulk operations validate each document in the batch, which could impact performance depending on the complexity of validation rules.
Updates (updateOne/updateMany) validate only modified documents, which generally results in a lower impact.2 votes -
Understanding the billing difference between Data Transfer and Atlas Data Federation.
It would be helpful if there was a chart or image that showed how data moves through the infrastructure and for each billing category.
For the Mongo folks, see case number 01327993 for more details.
2 votes -
The invoice the period should be:
Invoice period nedd to be changed as:
The invoice the period should be mentioned as "August 1, 2023 – August 31, 2023" instead of " August 1,2023 -01 September 2023"
2 votes -
Request for Beginner-Friendly, Topic-Wise MongoDB Documentation with Examples
Hello MongoDB Team,
I would like to kindly request that the documentation be made simpler and more beginner-friendly. At times, the current documentation feels too advanced, which makes it difficult for newcomers to fully understand. It would be very helpful if:
Explanations were written in simple, easy-to-understand English.
More practical examples were included for each feature or concept.
The documentation was organized in a topic-wise manner (step by step), so beginners can learn in a structured way without feeling overwhelmed.
MongoDB is a powerful and amazing database, and making the documentation more approachable for beginners would help many developers adopt…
1 vote
- Don't see your idea?