Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1334 results found
-
Allow the image export using Atlas Admin API
For the report purpose, we need to get the exported images of Status/Hardware/DBStast.
With personal authentication, I can get these images via URL:
https://cloud.mongodb.com/export/v2/charts/{status/hardware/dbstast}/{clusterID}/{hostID}/{format}/{title}?since={since}&until={until}&hostDbStatsName={DBName}However, I cannot get it programmatically with API Key authentication.
Let's allow the image export using Atlas Admin API.
Thanks!3 votes -
Support Linode as a cloud service
Linode is a widely used cloud provider between developers that do not like the outrageous interface & costs of the main providers (Google, Atlas, AWS). Linode has free in-network bandwidth as well, making for private connections to be much cheaper.
3 votes -
Support for customer-managed keys (CMK) on the volume-level instead of Encryption-at-Rest
For some customers managing a set of low-latency workloads is crucial, so volume-based encryption using their own KMS encryption keys is preferred over the encryption-at-rest feature of the WiredTiger storage engine. https://docs.aws.amazon.com/kms/latest/developerguide/key-policy-modifying-external-accounts.html
The support is required for clusters, their backups and Atlas Data Lake.3 votes -
Please add a debit card payment method.
Some countries use debit cards primarily so it would be great if we could have that option as a payment method.
3 votes -
Ability to get collection stats via the API
e.g. list collections, collection size, collection indexes, etc.
3 votes -
Add a simple log filter in the Atlas log API call
In the Atlas log API call, add a new Request Query Parameter which allow people to set a phase or string, to avoid downloading log lines including this phase or string.
So people don't have to download large quantity of log messages that they don't need.
For example the the NETWORK log message between replica-set members.
3 votes -
Improve handling of ROLLBACK state
Recently we had a member of a replica set in a sharded cluster enter
ROLLBACKstate. We just happened to notice it in an automated email sent by Atlas about primary elections which showed one of the members inROLLBACKstate.Fortunately for us the writes which had been reverted were not critical and we were fine with that. However, this could have resulted in serious data loss which could have gone unnoticed until a customer reached out to us.
The handling of a situation like this one should have been much better and more user friendly. We should have…
3 votes -
Access key expiration date
We would like to have option set expiration date time while creating API access keys and also ability to check expiration options through API.
3 votes -
Preserve Oplog upon storage downgrade in Azure
Oplog was wiped out upon storage downgrade from 128Gb -> 16Gb, even though the database size incl. oplog was less than 2-3Gb.
Please change the downgrade procedure to NOT wipe out the oplog.
This was tested/experienced on Azure.
3 votes -
Add option to alert on "degraded" state of cluster
I would like to setup an alert for the cluster state 'degraded', which isn't available as an option at the moment. Could you consider adding this as an option?
3 votes -
Display better Slack notifications
Currently, MongoDB Atlas Slack integration only send RAW text.
For easier reading, it would be nice (if not a must have) to leverage Slack notification format to have colors that represent at least the state of an alert.
Here is a suggestion from common things we can see in other tools:
* alert.open: Red
* alert.close: Green
* alert.update: Yellow
* alert.acknowledge: Grey
* alert.cancel: Brown
* alert.inform: BlueBonus: Leverage Slack App capabilities and have a
/command to acknowledge an alert directly from Slack.3 votes -
Document Atlas Cluster Tier Performance Expectations
Document approximate Atlas cluster tier performance expectations that application development teams could reference when requesting an Atlas cluster (IOPS, max connections, network performance).
This information is currently available in the Atlas UI.
Other cloud providers such as CloudAMQP do this: https://www.cloudamqp.com/plans.html.
3 votes -
Allow custom duration for Temporary Users
In our software development lifecycle, we have sprints that are 2 weeks long.
We create temporary users for Software Engineers that are "onCall" during a sprint. The role is moving to a different engineer each new sprint.
It would be great to be able to specify an explicit
deleteAfterDatevalue or a custom duration greater than the current 6 days.3 votes -
Create TTL index based on local timezone as opposed to UTC time
Create TTL index based on local timezone as opposed to UTC time
3 votes -
alerts on specific database
I'd like to setup an alert on my cluster for specific database but currently I can only setup alerts for all databases on my cluster. for example, send alerts when "Document Metrics: Deleted above 1" on zyz database
3 votes -
Allow domain or URL for whitelisting
Currently Atlas IP Access List entries allow to specify only either a single source IP addresses or ranges of IP addresses using CIDR notation. It would be great if user can add a domain or url for whitelisting where the IP address or range is not static.
3 votes -
Improve Cluster Name Limits
Cluster names currently impose the following limits:
Cluster names shorter than 23 characters can't end with hyphen or dash (-)
Cluster names 23 characters or longer can't use a hyphen or dash (-) as its 23rd character.
Instead, we should either trim or replace the hyphen at the end of a 23 character name.
3 votes -
migration should check actual disk space used by source MongoDB
The easy migration system seems to check the total disk space used on the source machine, and does not discriminate between that disk space used for MongoDB (which will be needed on Atlas) and those used for other applications.
Because the source system contains a lot of logs and a complete copy of our databases in different folders, we have had to configure Atlas to use >2x the actual disk space it'll need.
3 votes -
For resource mongodbatlas_cluster all properties related to provider move to separate block
Current resource
resource "mongodbatlas_cluster" "cluster" { project_id = var.project_id name = var.cluster_name disk_size_gb = var.disk_size_gb num_shards = var.num_shards replication_factor = var.replication_factor auto_scaling_disk_gb_enabled = var.auto_scaling_disk_gb_enabled mongo_db_major_version = var.mongo_db_major_version //Provider Settings "block" provider_name = var.provider_name provider_disk_iops = var.provider_disk_iops provider_volume_type = var.provider_volume_type provider_instance_size_name = var.provider_instance_size_name provider_region_name = var.provider_region_name provider_backup_enabled = var.provider_backup_enabled }Suggested resource
…resource "mongodbatlas_cluster" "cluster" { project_id = var.project_id name = var.cluster_name disk_size_gb = var.disk_size_gb num_shards = var.num_shards replication_factor = var.replication_factor auto_scaling_disk_gb_enabled = var.auto_scaling_disk_gb_enabled mongo_db_major_version = var.mongo_db_major_version //Provider Settings "block" cluster_provider = { name = var.provider_name disk_iops = var.provider_disk_iops volume_type = var.provider_volume_type instance_size_name = var.provider_instance_size_name region_name = var.provider_region_name backup_enabled = var.provider_backup_enabled3 votes -
support external nodes
Allow manual addition of externally-hosted non-voting (hidden) node(s) to an Atlas cluster. This would permit:
- compliance with data management rules that require a copy of all data to be kept in-house (ie outside cloud)
- easier migration out of Atlas for real-time DB use cases where a stop/backup/restore is not a feasible route3 votes
- Don't see your idea?