Documentation
13 results found
-
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!
1 vote -
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.1 vote -
There is lack of documentation for setting up Azure Private link
Almost no information provided for working with your Atlas cluster from another region. We have set up a private link in UK north while your cluster was in Netherlands. Private link was green but connection was not happening. You need to work it out.
thanks, V
1 vote -
Make documentation consistent for Atlas and Self-Managed MongoDB
You may review the entire documentation for MongoDB regarding Atlas and Self-Managed MongoDB.
The current documentation has some good pages, for example
Self-Managed Configuration File Options: It clearly states, this page is valid only for Self-Managed MongoDB and does not apply for Atlas.
Other pages are not so clear and especially for beginners they can be very confusing.
For example db.createUser(): Commanddb.createUser()does not exist on Atlas, however this is not mentioned at all in this page.Another poor example is Deploy a Self-Managed Replica Set: Despite the headline refers to Self-Managed MongoDB, in the middle…
1 vote -
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.
4 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.
1 vote -
Please Provide Documentation in 'Dark Mode'
It's very difficult and very painful of reading documentation for long time. It does negative effect on eyes. So, It's my request to provide a Dark mode of MongoDB documentation.
2 votes -
Hearing impaired accommodations
I have trouble hearing and understanding the narrator in the instructional videos please provide closed captioning, or at least the option for it? It takes me quite a bit of time to get through a single video because I have to keep rewinding it to make sure I fully heard the narrator.
1 vote -
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.…
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"
1 vote -
Missing piece of code in "Connect to Cluster"-Example
I think there is a missing piece of code in the generated code-example to connect to the atlas-cluster via Node.js driver and X.509: The definition for "const credentials" should be
"const credentials = fs.readFileSync('<path_to_certificate>')"
instead of
"const credentials = '<path_to_certificate>'"2 votes -
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
6 votes -
Actual API Documentation
There is various documentation for the many Realm/Stitch SDKs but almost no information about the underlying API endpoints, this needs to change and we need some detailed docs for working with the API itself.
I am trying to get an app running with the GraphQL API but have found working with the authentication APIs to handle auth tokens and sessions to be a bit of a nightmare. This page https://docs.mongodb.com/realm/graphql/authenticate/ has some useful information but doesn't even give the endpoints for logging out or explain how to properly handle the email sign up process using API endpoints in place of…
19 votes
- Don't see your idea?