Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1349 results found
-
Make collections scrollable
We have databases with many collections. The problem with that is that in order to select certain collection, I have to scroll the results part of the page. So I'm going up and down all the time I select another collection and make some query.
In sum, please add scroll in the collection explorer UI.
Regards
4 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 -
Increase maximum storage size for M60 servers
Currently the maximum storage size allowed for an M60 tier is 4TB. Our cluster is approaching this size, and we're facing having to shard our data, which we would really prefer not to do.
I understand that the maximum sizes are selected for performance reasons, but not every cluster is the same - ours is doing just fine and not struggling at all at this data size, and we would like to be able to continue to grow over time.
4 votes -
Replace editor with MLab's editor
Get rid of the dropdowns and give me a text box. Or at least an option to toggle off type safety.
I see the strength of Mongo as being untyped, but this editor is forcing in type. In addition, it is incredibly clunky to use when adding new fields by hand.
1 vote -
Allow Atlas User Data Access Permissions to be configured on a per-database/collection basis
Similarly to how database user data access permissions can be configured on a per-database or per-collection basis, it would be ideal if Atlas user data access permissions (as they apply to Data Explorer) could be configured on a more granular basis as well.
13 votes -
Precautionary Change/Recommendations for Shard Drops
If a user submits a configuration change to drop a shard, Atlas will sift through the cluster metrics and advise any necessary changes needed in order to complete the change without any errors/delays. For example, it will share the correct number of IOPS/cluster tier that needs to be used since the workload to drain a shard will increase; as well as other precautionary measures that should happen prior to dropping the shard (i.e. balancer needs to be turned on, etc).
2 votes -
Cloud backup to new cluster
Two different ideas for this:
-When building a new cluster having the option to build it using a cloud backup snapshot for DR when a cluster is down-Same idea to restore to a new cluster but from the restore target dropdown IE Restore to New cluster which opens the create a cluster workflow with the cloudbackup snapshot section populated
6 votes -
Need an easier way to issue multiple document operations within Atlas online or Compass.
Provide a method to perform commands such as updateMany()
1 vote -
Ability to add multiple IP's to the whitelist and download the current whitelisted IP's
If I want to add comma separated IP's it is not possible. We have to add each IP painfully from the UI. Please allow to add comma or semicolon separated IP's to be added at once.
Also, why can't I download the current whitelisted IP's as a CSV or other file?
4 votes -
Improve online archive Status
add more to the status of the online archive - for example, if I set it to 7days back it's good to know that currently at 80days.
An example: for a very big collection it takes long time to archive - so either show a % left until it caught up or show number of days currently at
other nice details: number of documents archived, archive rate, etc
9 votes -
Time based auto scaling
Our production server workload is less after 5 pm till the next day morning at 6 am CST times. We are running MongoDB in full capacity even on off-peak times. It's not possible for someone to manually downscale the cluster during off-peak and I don't think the CPU utilization based auto-scaling is working for us. I would like to choose auto-scaling between CPU based or time based as set my own time window and choose the auto scale/down-sclae.
70 votes -
Alias for Cluster name
Add an alias to cluster name, as we are not allowed to change the cluster name. If we have an option to add an alias to cluster name. We can use it, in-case the user created the cluster with the wrong name. And in-screen u can show as clustername(alias). For better understanding.
1 vote -
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…
2 votes -
Show index name/details when creating or dropping index via Data Explorer
When Atlas user creates a rolling index in Data Explorer, we can see the name of the index being built in Activity Feed. However, if Atlas user creates an index or drops an index, the index name is not revealed in Activity Feed. This creates some complexity to trace which index is created or dropped via the Data Explorer
1 vote -
Force restart of unhealthy node
Right now, there's a "test failover" option, which shuts down the primary and forces an election. However, the option is only available if the cluster is in a healthy state.
If, for whatever reason, the cluster is unhealthy, it's impossible to manually restart the primary. It should be possible to force an election in an unhealthy state. Often, this is all that is required to get back into a healthy state (e.g. if the primary is in a CPU burning loop that was caused by an unexpected write pattern that has stopped.)
115 votes -
Trigger event when user confirmation state change
I suggest that after user registered they should ve able to log in regardless of his account confirmation state, but if he is in a pending state, he could not do any read/write operation unless his own user data and his own user extra data,
And the user can also detect if his confirmation state is change
1 vote -
Expose the killOp() action when creating custom roles in Atlas UI
It would be nice to have the
killOp()action exposed when creating a custom role in Atlas.I also think it would make sense to grant this action to the
atlasAdminrole, but at a minimum I feel that Project Owners should be able to create a custom role that is allowed to kill ops that were initiated by other database users.16 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
- Don't see your idea?