Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1362 results found
-
Unevenly Scale Global Shards
Globally distributed shards should be able to scale unevenly. We have uneven loads across the world and sometimes spikes can hit a single region. Autoscaling for that single region scales everything and increases costs unnecessarily
3 votes -
mongoexport with Client Side Field Level Encryption
I would like to have mongoexport and mongodump tools with Client Side Field Level Encryption /Decryption. Please consider while developing new feature.
3 votes -
Disk throughput in monitoring
Currently we have disk IOPS in monitoring (both read and write).
One of the metrics that play a role to decide whether to have a provisioned disk or not, at least with AWS hosting, is the disk bandwidth.
For instance with a large enough disk, like 2000GB, I have max 250MB/s bandwidth with an unprovisioned (gp2) disk (the maximum), but could go to 500MB/s with a provisioned (io1) disk of that size.3 votes -
Allow triggers to be tested locally
Our team uses and loves Stitch/Realm triggers. We've got them wired up so that we can update them from a bash script. They work well, but they are hard to debug -- it'd be nice if there was a CLI option to test them against a local mongodb instance.
3 votes -
More detailed update status
It would be amazingly helpful to see more detailed information on recovering nodes. Just knowing that the node is, for example, "81% of the way on initial sync" is much more informational (and lets users know that it isn't stuck) as compared to the node being in "Startup2" recovery.
3 votes -
Add a Transaction Commits / Sec Metric Graph to Atlas
Add a graph in Atlas to display "transactions.totalCommitted" on a per second basis to the Atlas metrics UI. Customers that are using transactions are often more interested in the # of transaction commits per second than opcounters.
I have had to use mongostat on a number customer evaluations because this metric is not available.
3 votes -
Allow 'Download Logs' for user that is not a Project Owner but Project Data Access Read Only or Project ReadOnly
Currently in order to allow a user to download logs, it is necessary to make that user Project Owner. In a situation when a user outside the company is invited to review the project, it is not possible to grant such high level role when the access needed is only to look at logs. Project ReadOnly or Project Data Access ReadOnly should be sufficient to access logs, if the user is also granted atlasAdmin@admin access to Database
3 votes -
Publish statistics in Atlas to analyze what is filling oplog
It would be very useful to be able to see metrics/statistics about the contents of oplog. There are open-source tools like oplog analyzer (https://github.com/mhelmstetter/oplog-analyzer) that can be used, but it's a hassle to have to install it and run it in the same datacenter where the database is running (for performance).
The statistics I'm most interested is what collections have most oplog documents, what kind of operations they have been and what is the total size that each collection currently utilizes from the oplog. This will help improving code to use less oplog.
We've seen cases where bad…
3 votes -
The page fault metric is not available in the Datadog integration
The page fault metric is not available in the Datadog integration
3 votes -
Real Time data explorer
I would like to see documents inserted into the database in a shell show up on the cloud data explorer UI in real time without refreshing the screen.
3 votes -
Better message for "Removed Indexes" in Activity Feed during Atlas rolling index build
During a rolling index build, it is expected to have 2 "Deployment configuration published" notifications - 1 for Added Indexes and another 1 for Removed Indexes. This is because an entry for this desired index is added to the automation config and then the automation agent builds it accordingly. Once the agent is done building it, we remove the entry for that index from the automation config. Indeed, this does not drop the index.
However, from the term of "Removed Indexes", it can cause confusion that the index is dropped. Hence, this feature request is filed for clearer message so…
3 votes -
It would be great to have a tool with historical data about database and collection.
It would be great to have a function where we can , using only atlas interface to filter a month and a year , and we cann see historical data about sizes.
3 votes -
Permission level to query snapshots
Right now I have to give an admin permission to allow someone on my team to query snapshots from a backup (i.e. downloading the tunnel file).
I don't want to give an admin permission just to allow our data analysts or a developer trying to understand data corruptions to view the database at an older date.3 votes -
'Find' should offer a JSON mode
Under Atlas > Clusters > Collections I can select a Collection and use the 'Find' option to quickly seek and edit a Document. At the moment the UI display is like JSON, but has stripped out the brackets, which makes copying the data awkward.
Feature 1: The find display UI should offer a JSON mode, so the the Document, or parts of it can be copied in JSON format.
If I select the Edit option, the editing UI is 'intelligent', in that it forces JSON compliance via the various options. However, this makes pasting in new data impossible.
Feature 2:…
3 votes -
Live Migration Should Include Database User, Password and Role Information
Please provide the option to include database username, password and role information during a Live Migration. DBAs often do not have direct access to database credentials and have to collect them from the various development teams.
3 votes -
Add SHA-256 as Digest Authentication Algorithm for API
For compliance with NIST and other standards, it would be preferred to use SHA-256 as the algorithm for digest authentication for the public API as opposed to the currently implemented MD5.
3 votes -
Provide a granular mechanism to disconnect and disable all active sessions during a planned maintenance.
Provide a per cluster mechanism to shut off client access for restore operations.
3 votes -
Clarify Python vs PyMongo
When connecting to a Atlas cluster and selecting to connect via a Application you can select to connect with what "Driver" where you can select "Python".
For new users, they might think that the Python library (https://www.python.org/doc/versions/) is what is being referenced when in reality Atlas is referring to the PyMongo Driver.
For clarity, alter the UI from "Python" to "PyMongo" or "Python (PyMongo)" or something similar to differentiate between Python and PyMongo.
3 votes -
Smart backup scheduler (deferring snapshot backups X minutes based on load metrics)
seems like a potential enhancement for the snapshot schedule to consider cpu/connection/etc load metrics before deciding to run or not
3 votes -
Support for AWS KMS CMK per cluster (instead of on a project level)
Hi Team,
Currently, we have KMS CMK configuration available on the project level.
We are hoping to see if that can be changed on cluster level.Reason: Once we update the key, all the clusters will get re-encrypted with new key, but snapshots will not be re-encrypted with the new key.
For any reason, if we need to restore snapshot of one particular cluster, we will need to update KMS key with the old one, which impacts all clusters to get re-encrypted and then only can restore.Hence we believe cluster level KMS setting would be beneficial in such a…
3 votes
- Don't see your idea?