Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1262 results found
-
Cluster events - create, modify, delete
Add an alert category for cluster scale events such as creation, modification and deletion
6 votes -
Cancel restore
There should be an option to stop once the restoration is given. Or there should be an option to revert a backup restore. This is required because we can restore an old production back up to Production only. If by mistake we do that we should be able to revert back.
6 votes -
Show date in UI DB Stats axes
Show date in UI DB Stats axes
Currently the x-axis of DB Stats charts do not show dates, making it difficult to interpret the range of time displayed in the chart.
For example, you can see in the date menu shown in the attached image that the chart range is over 4 days, but this is not apparent in the x-axis of each chart -- the x-axis only shows one reference time of 07:00.
It would be more helpful if the axis showed a reference date in addition to the time, and ideally a couple dates so that it is…
4 votes -
I would like to have ability to generate an Excel file for clusters in the Organization
I would like to have the ability to generate an Excel file for clusters in the Organization.
https://cloud.mongodb.com/v2#/clusters1 vote -
Show last activity of user
For managing Database Users, it would be nice to see when that user was last used to authenticate with the cluster - so that we can spot potentially unused accounts and to act as an extra layer of confirmation when deleting accounts that we think are not needed anymore.
8 votes -
Have the capability to manage contact details for Atlas-level 'Teams'
There should be a capability to manage/assign contact details (such as email) at the Atlas level, to the created organizational 'Teams' (such as assigning a team distro email address), so that alerting can be streamlined, instead of sending out separate emails to each and every member of the team.
1 vote -
Create location key in all documents for sharding in data explorer for Global Writes
I would like to develop in new Global writes cluster for an existing data base model create easily and fast the "location" key in all documents from collections that Global writes requires.
1 vote -
Left Side menu collapse
on the laptop screen, we have't much space for querying the data filter portion. If we have an option to collapse the left side menu, it may get more working space.
1 vote -
Show BI Connector resource use Metrics
It would be helpful to be able to view the resources used by the BI connector in Metrics, similar to how you can view resources used by Atlas Search (Search Disk Space Used, Search Normalized Process CPU, etc). This could help with identifying issues due to resource intensive queries submitted through the BI connector.
Currently it is only possible to guess that an issue could be related to the BI Connector by viewing system resource use.
2 votes -
Allow to provide names/descriptions for peering connections
If the user has 3 peering connections in a project, it's error prone terminating one, as you may end the connection with the wrong VPC and cause a disaster. Adding a description field allows to clearly see the purpose of the peering.
1 vote -
Cluster Update Details in Activity Feed
When a cluster update happens and things change such as the certificates, why wouldn't this show in the activity feed? The only thing noted in a recent issue we had was "cluster update". If we could see the details of the update we could have resolved our problem quickly without opening a case.
6 votes -
real time view for just one node
Given that I address certain kinds of queries to certain tagged nodes,
As a developer,
I would like to filter the "real time view" tab to show only activity for my tags
So that I can monitor how my application impacts its node1 vote -
audit log event when new project is created in an organization
add an audit log even when any user within the organization creates a new project. Currently you can see when a collection is created, but nothing for new projects. This is helpful for auditing and accountability purposes.
1 vote -
API Key Expiration date
We have a security reqirement that secrets must expire after 2 years.
Therefore it would be awesome if MongoDB Atlas API Keys would support an expiration date.
Somethig similar exists for the IP Whitelisting. Here we have the option to remove IP Whitelist entries after er certain time period. But for API Keys it would be better to have an expiration date and keep the API Key in the list even if its expired.
In addition it would be good to have a daily notification once the expiration date is ahead less than 30 day.
14 votes -
Profiler output is confusing
Not so much a feature perhaps as a bug, but it seems that in the profiler page, the chart changes with the time window of interest, e.g. from 24hr to 6 hr or 1hr, but the listing of the namespaces underneath does not. So suppose you think you've fixed an issue and want to check 4 hours later. The chart seems to indicate things are ok, but the namespace table is actually confusing in this case. When you click on an item in a listed namespace (i.e. collection), it goes into the detail view and that one does conform to…
1 vote -
Bytes available for reuse metric
This metric will show the available bytes for reuse. If it's too much and its graph is changed a little bit, we can decide to compact it for saving cost (from disk usage).
Currently, we have to run dbstat command to see the available bytes for reuse and can't know its trend.2 votes -
Accept Cryptocurrency Payments
Accept cryptocurrency payments for billing purposes as Paypal or Cards are very unreliable. Recommended cryptos - Bitcoin (BTC), Ethereum (ETH), Bitcoin Cash (BCH), Dash.
Commerce between users and mongoDB platform will greatly improve by allowing payment mechanisms that have instant transactions at a much lower fees.
3 votes -
improve error messaging
We are running into misleading error messages that learners are complaining about. This error appears when a user tries to use a $limit stage and forgets to add a $ while connected to a Free Tier Atlas cluster:
"OperationFailure: limit is not allowed in this atlas tier, full error: {'ok': 0, 'errmsg': 'limit is not allowed in this atlas tier', 'code': 8000, 'codeName': 'AtlasError'}":
This has been confusing for users. Is there a way that we can catch this issue more precisely and issue a syntax error instead?1 vote -
Add information to the billing API reponse
When retrieving the billing details through the API, we are missing some information for a perfect understanding (and automation) :
- Number of nodes of the cluster. Indeed, without this information, the field "quantity" is kind of complicated to interpret
- Group Name. Each entry is attached to a groupId, but sometimes when the project has been deleted, it is impossible to retrieve its name, so pretty complicated to interpret (in the UI, the group name is available, so I guess it can be in the API)
12 votes -
Support ISRG certificate selection in mongodbatlas_cluster
As described in https://docs.atlas.mongodb.com/reference/faq/security/ and a recent email announcement, the root certificate is changing. Changing the cert used is available in the UI, but not in the provider.
It would be useful to add support for certificate selection.
1 vote
- Don't see your idea?