Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1258 results found
-
Hello, your login captcha is a real pain ********** !!!!!
Hello, your login captcha is a real pain ********** !!!!!
1 vote -
Alarm on potential data breach events
Provide capability to raise alarms on specific events like mongodump, mongoexport (eventually mongorestore, mongoimport)
5 votes -
Code support
Your website is a monster where is very difficult to get the useful information.
I wanted to use Realm to use a mongo cluster and after hours trying I give up.
I couldn't connect to the cluster after I created serveral ids (app, api, another api id, ...)Solution: Let's say I have a single cluster and a single realm app created.
Just give me the code with all the ids necessary.In my case I wanted to run it from the browser.
This is the code I tried to execute:
…const app = new Realm.App({ id: 'tradeapp-bozmd' }); const1 vote -
Atlas Role
The idea would be to have more advanced options when configuring access management to different projects/clusters.
A lot of companies would benefit greatly from seeing a segregation of roles and access to different features on a project.
It would be beneficial to have more read roles - focus on the metadata layer, but it would be also nice to have it on the DB level e;g. Onboarding a local entity - DBAs want to see only dedicated DB information - should be then between their responsibility.
The idea is to have differentiation between metadata and data, It can be particularly…
1 vote -
Atlas project capacity should be discoverable
Atlas project capacity should be discoverable. Based on documentation, it seems project capacity is dependent on various factors and can be arbitrarily increased via support request. We currently do not know how many clusters/nodes we have available to deploy in a given project and that is critical information to inform planning at scale.
5 votes -
Kubernetes AtlasDeployment snapshot persistence flag
When AtlasDeployment resources are deleted, the cluster is immediately terminated without the opportunity to enable snapshot persistence after deletion as there is in the Atlas UI. An option in the spec should be added to opt-into this behavior from a Kubernetes perspective.
1 vote -
Backup persistence after termination should be standard
It is odd that snapshots are tied to clusters and lost/destroyed when clusters are terminated. Snapshots have their own retention policies for a reason. Persistence after cluster termination should be the rule, not the exception.
5 votes -
Kubernetes AtlasProject backup compliance
Extending the AtlasProject Kubernetes resource to allow management of a backup compliance policy, including setting project-wide backup schedules and enabling backup persistence after termination by default, would be a major improvement over the current experience.
1 voteIt will be coming in a release in the next few weeks!
-
Kubernetes reconcilation interval
Kubernetes resources generally should be reconciled on a sensible schedule to prevent configuration drift between k8s and Atlas API.
AtlasProject is a critical one that can have widespread impact if API configuration drifts from Kubernetes and is not promptly corrected.
1 vote -
DataDog integration: add metrics for any current resource limits
We're using the DataDog integration to bring MongoDB metrics to DataDog. We want to re-create a DataDog monitor which is an equivalent to Altas alert "Connections of configured limit has gone above <>". However, we cannot do that relying solely on metrics, since the only connection related metric we found is "mongodb.atlas.connections.current".
It looks like the only way to solve this issue is to create a DataDog monitor based on the received event from Atlas.1 vote -
Retrieve latest/max oplog timestamp via the Atlas Administration API
At the moment the latest/max oplog timestamp can be retrieved via the Atlas UI in the backups section for point in time restores. This feedback post is to make this information available as part of the atlas administration api.
For example, in the UI it states:
You can only restore up to this oplog timestamp: 1692580549 and this increment: 1.
Would be good to have this value available to be retrieved via the API for restores requiring oplog timestamp values in this format.
3 votes -
Enable database users separate read/write permissions based on cluster
We have multiple clusters in the same project, and we need to limit write access to certain CLUSTERS while leaving read only access to any other cluster. The problem is that we cannot do this by DATABASE name as there are many of them, as well as dynamically addition of new ones in clusters, so it will become obsolete and very hard to maintain.
Trying to use the restriction does not help as it limits all access, including read only, to those clusters.
What we'd like to see is that we can limit write access by cluster (not database/collection) and…3 votes -
Integrated Benchmark utility for mongodb
I would like to request a mongodb utility which can do benchmark tests and can be used by developers and DBA to test mongodb for release changes, application code changes etc. The utlity should be able to simulate multiple users and produce different types of workloads (like reads, updates, deletes, inserts etc). This would need to be similar to other nosql benchmark tool like asbench used in aerospike nosql database.
Link is : https://docs.aerospike.com/tools/asbench4 votes -
Hyperlink to "all cases" that's under the "create new case" link
To access the support portal from the projects page:
- Navigate to Support to the left side of the page
- Click on Visit Support Portal button under Request Support
It will be easier to navigate if a hyper link of "all cases" can be added to "create new case" from the "get help" drop down as in screenshot attached.
2 votes -
Monitoring Metrics on dhandle
We'd like to monitor the WiredTiger dhandle over the time, directly from Cloud Atlas Monitoring view. It would allow to directly see the impact when updating cluster settings.
We'd like also being able to configure alert triggers on it, the goal for us is being alerted when an excessive amount of files (collections & indexes) is loaded into the MongoDB Memory, to avoid reaching an Out Of Memory error.
2 votes -
Improve Atlas suggested indexes
Suggested indexes
- Currently it will suggest indexes that can't be created, such as with multiple array fields.
-- This should be detectable before suggesting an index.
-- Highlight array fields in the suggested index
- Include partial index expressions
- Make more than one suggestion for queriesTrying to create an index that contains multiple array fields (for some documents being indexed) won't fail until it hits one such document.
- Pre-parse to first confirm the fields being indexed don't include more than 1 array for the index?
- Pre-parse and inform the user if any of the fields…2 votes -
LDAP Users shouldn't be successfully authenticated if not authorized
Today, if you login with proper LDAP credentials to an Atlas cluster, you are authenticated into that cluster, even if you are not authorized to have access. This is not at all how databases should work, nor is it how most databases do work today. If a user is not authorized, that connection should fail immediately.
Allowing successful authentication, even when not authorized, can increase the security vector for ddos attempts as well as causes confusion when successful attempts are logged, even though the user was not authorized to see data.
Please reject any non-authorized user from connecting to an…
4 votes -
Exponential Backoff
Exponential Backoff:
Data come from AWS event bridge, connection issues happened
Exponential backoff would have helped that that this connection issues are recognized and the customer would not have intervened manually.
There was no alarm once trigger was suspended - an automatic alarming would have been helpful.1 vote -
Duplication detection
One of our custmoers would like to see duplication detection as their project is spread out over various projects.
Value: It is important as different regions create sometimes duplicates and duplicates can be avoided in advance.
1 vote -
Add document count to Datadog metrics
We'd like to monitor the number of documents in a collection via DataDog.
For On-Premise MongoDB the stats are already reported via mongodb.collection.count, mongodb.collection.size and mongodb.collection.avgobjsize.
If the same metrics could be made available for Atlas (E.g. mongodb.atlas.stats.collection.count) that would really help in monitoring.
E.g. spikes in different parts of the application could be tied to the number of documents on a glance. Without having that metric available, it is hard to pinpoint if a recent change had a negative impact on performance.
If the metrics can't be made available on the collection but only on the database level, this…
8 votes
.png){kind=link}
- Don't see your idea?