Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1366 results found
-
Use 24-hour time format in Metrics date pickers
Timestamps in Metrics plots are displayed in 24-hour time format, but the date/time filter inputs require 12-hour time (using am/pm).
12-hour time is not widely used around the world, and it is cumbersome to use in the date pickers especially give that other parts of the UI use 24-hour time.
Can we update these date pickers to use 24-hour time instead?
6 votes -
Show in the UI when an index build is ongoing, and when it completes
When indexes are built from an application or a mongorestore there's no way to see if it's ongoing in the UI.
There should be an indication in the "Real-time" tab saying that an index on collection X is in progress. This would explain why performance is currently impacted.
It would be good to see index start and end marked on the "Metrics" visualizations so we can see the impact of index builds on IOPS, CPU, memory etc. This could help understand if we need to upscale the cluster.
10 votes -
Unique VPC Peer CIDR
Prevent the same VPC Peer CIDR block, is it currently possible to have 2 projects with same CIDR block, which requires us to delete our clusters and peer before creating new clusters
There should be a way to prevent them from having same CIDR block or the ability to change the CIDR block AFTER they are created
8 votes -
Show Cursor Not Found Errors (telemetry)
We have a lot of cursor not found errors and currently there isn't an easy way to locate them at the Atlas integrated monitoring.
It would be nice to have this feature.1 vote -
View dashboards as if another user
As a Project Owner, when I start rolling out dashboards to new users, I would find it very useful to see the dashboards as they can see them with their current permissions. I would like to be able to "View As" a particular user, so I can see that I have granted them the correct set of dashboards and test their permissions work for them. Obviously a feature for Owners only.
2 votes -
Add full screen mode for multi-graph Metrics and Status views
Unless I've missed a button somewhere, it would be nice if the "Metrics" tab for clusters and "Status" tab for shards had an option for expanding the entire tiled graph view into a full screen view. We have some TVs around our dev pod where we display these graphs and it would be great to see several graphs at once in full screen view.
2 votes -
Create Zurich region as option for AWS deployment
Atlas already supports deployment to Zurich region for GCP. As a reasonable option, introducing AWS deployment to Zurich zone would be benefitial.
6 votes -
Ability to search for filter conditions in Atlas Alert builder
It would be helpful to be able to search for a trigger condition in the Alert builder when creating/editing an alert.
Currently, you need to scroll to find specific conditions, but the list is long so it can take some time to find the particular one needed.
5 votes -
Atlas activity feed
We want option to export Atlas activity feed in a file to export and work with it. Parse it etc ...
Even better, make a collection with it.
7 votes -
Ability to customize the name of the invite sender in emails when inviting users via API
When inviting new Atlas Users to organizations via the API, the invite email says that the invite was sent by the API public key that performed the API call. This makes the invitation emails read like this:
"You have been invited by tfqzvwrs to join the Example - Atlas organization on MongoDB Atlas."
The ability to customize this (e.g. using an additional field in the request body) would be ideal since the random string being shown as the sender of the invite could make the email look suspect.
1 vote -
Show shard node name in alerts
When receiving tens of emails regarding a dangerous condition on a node it would be helpful to know which node instead of having to click in the email to get to the portal to know if the issue affects our primary node or a secondary node.
Thanks
1 vote -
Deactivate use of charts on org-level
As charts meta data are processed only on US servers, a toggle to forbid the usage of charts for autonomous teams would be helpful, considering GDPR requirements
2 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 -
Provide an option to block access for certain username and source IP
We would like to provide users an access to database from our VPN to browse the data with some database tools - this access should be read only. As for now if somebody connected via VPN and uses production credentials he will be able to write to the database. To be able to configure it I think Atlas should provide a IP whitelist/blacklist during the user creation becaouse global Access Lists are not enough.
1 vote -
Sort IP Whitelists in Atlas
Enable sorting and filtering on the whitelist management screen.
There is no logical order to the list of ips.5 votes -
Credits by period
Provide the ability to display and export credits by period (from date - to date) instead of selecting each single month, so that uers can easily display credit trends, etc. without downloading a lot of cvs and merge them togheter.
2 votes -
Count
Whenever a query is fed into the filter search box, ensure that the count of the result is also provided somewhere above the result of the query.
2 votes -
Add a grace period between a failure to obtain a certificate and the cluster shutting down.
If you set up encryption at rest on Atlas using an external key provider, such as an Azure Key Vault, then a link is created between being able to access the key vault and the status of the MongoDb cluster.
For example, on the 28th September, there was an issue at Azure (SM79-F88) and for over 2hrs around 19% of all authentication processes in Europe failed. This included accessing the KeyVault used by our MongoDb cluster. As Atlas checks the keys roughly every 15 minutes it failed to obtain the key at the beginning of this period and our cluster…
1 vote -
Shorter Temporary Durations for Network Access whitelist
Hello,
it would be nice if you could add options for temporary whitelist entries that are shorter than 6 hours. Often in our Team we find ourselves just needing to whitelist an ip for a short amount of time to look up some documents or fix a bug.
For that case it would be nice to have additional shorter options like 3h, 1h, 30m, 15m.Thanks for taking a look
5 votes -
Project Alerts: show details about "Closed Alerts"
In "Project Alerts" we can only see certain details about "Closed Alerts," e. g. for an "Index Suggestion" we can only see the timestamp and the fact, that there was an index suggestion. You can't see what the specific suggestion was. So if you look through the history of alerts, you cannot tell if for multiple alerts it was always about the same index to be created, or whether it was for different indexes.
Likewise, for "Daily amount billed ($) is above threshold" you can see that the threshold was exceeded, but you can't see what the specific billed amount…
2 votes
- Don't see your idea?