Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1310 results found
-
View Atlas user sign in method in logs or UI
We'd like to see how are users are signing into Atlas.
At the moment we can just see username, email and permissions.I want to see which Auth method they used to sign in e.g. email & password, GitHub SSO, Google SSO, AD etc.
1 vote -
Safe mode to pause non-essential changes
I'd like to be able to put the cluster into a "Safe Mode" during an incident.
For example, I'm responding to an incident or I suspect something's fragile or breaking, and I don't want any scheduled activities to make it worse or distract me. I also don't want to have to know what changes are scheduled, I want to pause them all regardless.
This would pause any scheduled or non-critical changes, like upgrades, building indexes, probably resyncs, etc.
But it would keep running cluster-safety/health-supporting mechanisms like auto-heal, and probably backups.
And it would put up a banner on the cluster…
3 votes -
EmbeddedDocuments Search multiple compound fields
Today, it doesn't seem that a $search index on a list of object documents allows for an embeddedDocument search to match on multiple properties within the document.
So, if I have:
[{
name: 'Doc 1',
attached: [ { name: 'a', type: 'string' }, { name: 'b', type: 'number' }]
},
{
name: 'Doc 1',
attached: [ { name: 'a', type: 'string' }, { name: 'b', type: 'string' }]
}]I would like to be able to write a compound query like this:
[
{
$search: {
index: "default",
compound: {
must: [
{
embeddedDocument: {
path: "attached",
operator: {
compound:…1 vote -
Request for Enabling Vendor-Metered Tagging on AWS Marketplace
Hi Team,
We are currently utilizing MongoDB services via the AWS Marketplace and have encountered an issue related to cost allocation tags.
We have recently been working on improving our cost management and reporting processes within AWS.
A key component of this effort involves leveraging AWS-generated cost allocation tags, particularly those prefixed with "aws:marketplace:isv:".
However, upon review, we have noticed that these specific tags are not available or being applied to MongoDB services that we are using.The absence of vendor-metered tags for MongoDB on AWS Marketplace is hindering our ability to effectively track and allocate costs associated with your…
8 votes -
API change date format for log download
While programming a script to download the activity feed and audit logs, we found out that the date format which is accepted for API calls does not match. While the Activity Feed is fetched with a date in the ISO 8601 format (&minDate=2024-01-24T12:30:06.415944), the audit log accepts only an epoch timestamp (...?endDate=1702632210&startDate=1702625017).
This causes several conversion issues when automating log-fetching. To avoid these issues, we suggest changing the API call to use the same date format.
2 votes -
MongoDB Atlas historical stats by collection
It would be helpful to have historical metrics for storage by collection. Storage space used, indexspace used, number of indexes.
Thanks1 vote -
Support resource tags included in billing ingestion dashboard while filtering Charts billing dashboard by resource tags
It's important to support resource tags included in billing ingestion dashboard and filtering the charts based on these resource tags. Include the resource tags in Atlas billing dashboard as filter/group criteria
1 vote -
Reestablish private endpoint if in status "Rejected"
Create an AWS endpoint for connection with the (already established) MongoDB Atlas endpoint service -> AWS endpoint is in "Pending acceptance" status.
Establish the connection with "mongodbatlasprivatelinkendpointservice" -> AWS endpoint goes into "Available" status.
Destroy the "mongodbatlasprivatelinkendpointservice" connection -> AWS endpoint goes into "Rejected" status.
Recreate "mongodbatlasprivatelinkendpoint_service" with the same variables -> terraform does recreate he resource, but the resource is not functional.
In the MongoDB Atlas GUI it shows "Failed. Endpoint failed to reach available state. Click 'Edit' to fix the problem."
The problem cannot be fixed by using "Edit" !…
1 vote -
1 vote
-
Allow customization of where $merge creates the temp collection used when rehydrating data from Online Archive --> Atlas
When you restore data from the Online Archive back into your Atlas cluster (aka "rehydrate") you need to use $merge within an aggregation pipeline. What isn't documented is that $merge will create a temporary collection in the same database you're rehydrating to, which requires that you have readWrite@<dbName> privileges so that the new collection can be created.
For customers that operate on the "principle of least privilege," where you only grant literally exactly what is needed to accomplish database CRUD operations, the user would the more narrowly scoped "readWrite@<dbName>.<collName>" privilege granted to the user to scope the actions to only…
10 votes -
Support tagging individual replicas in the cluster
Thank for the support for the tagging at the cluster level during database deployments( https://feedback.mongodb.com/forums/924145-atlas/suggestions/43032180-support-for-tagging-clusters-in-atlas)
However it would be useful to have support for tagging individual replicas in the cluster.
For example., we want to deploy the same app as two deployments tagged as tier-1 and tier-2, with tier-1 deployment service accessing tier-1 tagged readonly replicas and vice-versa.
2 votes -
Improved deletion protection against malicious users
Currently, the only option of preventing malicious admin users from deleting a cluster with all its backups is to enable a backup compliance policy. However, this policy is quite the beast with complex processes and guarded by a single user account (which could then as well be the malicious one).
It would be good to have some less impactful way of protection against malicious users.
For example, when deleting a project in Google Cloud, an email is sent to all project owners and the project including all of its data can easily be restored within a period of 30 days.…
5 votes -
Support hourly backup every 24 hours, or support Point-In-Time restore without an hourly backup
To have Point-In-Time restore, an hourly backup policy is required.
However, the maximal interval for an hourly backup is every 12 hours.
I would like to take a backup only once every 24 hours, but still have Point-In-Time restore possible.So, please support either PIT-restore without an hourly backup policy in place, or support an hourly backup policy with an interval of 24 hours.
2 votes -
Allow to change defaultWriteConcernSource to global to avoid flipping the flag
Customers experience following error messages due to the defaultWriteConcernSource mismatch between the source and target cluster when restore the snapshot.
Error: Can not restore a snapshot with custom default write concern 1 to a cluster that does not have a custom default write concern.
Error: Can not restore a snapshot with custom default write concern majority to a cluster that does not have a custom default write concern.
Ability to directly change the defaultWriteConcernSource without flipping between w:1 and w:majority will be convenient for the users.
Option location:
Cluster > configuration > Additional Settings >
More Configuration Options > Default…2 votes -
SIEM
Add audit log integration with enterprise SIEMs
6 votes -
Improve Metric Correlation
Would be nice to better correlate metrics, server events, and individual operations.
For example would be helpful to have in the profiler indication of automatic scale up/down of the cluster in order to easily correlate actions that trigger them in the last 24h.
1 vote -
Metric Grouping
A huge improvement and help when it comes to metrics would be the ability to query by grouping (e.g. for database access users). This way if you were to use a specific database user per a specific service connection, we could see how much load to the database that specific service is causing.
Any form of implementation would be helpful, one example could be adding labels to the prometheus metrics per user, replica/shard etc.1 vote -
Profiler: expose the dashboard ID and chart ID from which the query is originating
My MongoDB analytics node performance is decreasing.
Looking at the profiler it seems that some specific queries are super slow.
I can see the full query, I can see that they originate from MongoDB charts ("appName": "atlas-data-federation|app-services|xxxxx").
But I cannot see which dashboard ID and which specific chart ID this query is originating from.
So I cannot, for example, easily find which chart to delete.Is this something you could help with? or any work around?
thanks!1 vote -
BI connector host name via API call
BI connector hostnames in the Atlas UI: https://www.mongodb.com/docs/atlas/bi-connection/ is not supported via API , Currently, customer has to manually copy and store the values to be reused by other applications. The customers are hoping to get these values in an automated way, for example with API calls or SDK.
3 votes -
All Clusters permission for ORG level roles
Today, for you to be able to use All Clusters you need to have permissions on each project, your user needs to be included in each project.
When we use a federation, we generally don't grant permission for each project to a team of administrators. We grant ORGOWNER, for example. By doing this, we lose access to All Clusters. The idea was to include the permission to use All Clusters for project-level permissions that have permissions to read project resources, for example ORGOWNER or ORGREADONLY.
6 votes
- Don't see your idea?