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
-
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.
1 vote -
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
-
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.
1 vote -
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 -
Throttle instances within a shared tier
Right now, if a cluster is in a shared tier, other "noisy neighbor" tenants can destroy performance by overusing the resources, forcing a restart, causing unstable behevior etc.
Throttle noisy neighbors so that others don't suffer!
1 vote -
MongoDb Atlas Network Peering with Oracle OCI (Similar to Azure and AWS)
Please add similar Atlas network peering capabilities as that of Azure and AWS, for Oracle Cloud Infrastructure customers. We are currently using Azure, but would like to use OCI as well.
1 vote -
AtlasProject CRD status fields
Hi, we have created the Atlas project via Terraform and used the mongodb operator for cluster and user management, but for now, we use sidecar to set the status.id field in AtlasProject CRD since we use skip-sync flag ( so operator will not change project config) and the operator will not sync this field for us.
If it is possible add a parameter to the spec where I could set this ID within resource creation ( so if we have a skip flag it will automatically set status.id ), so we can get rid of sidecar ( sidecar was implemented…1 vote -
View Epoch in Compass
I use epoch times in almost every collection for created time, last modified, etc. Currently I have to copy the time value and paste it into epochconverter.com. It would be very handy if the time showed as a string in a bubble when you hovered over it in Compass.
1 vote -
Larger disk for smaller cluster tier (instance type)
We have TB-scale data in production, and we also have several databases of the same-size for development environment.
Since Atlas's smaller cluster tier such as M20, M30 doesn't support large disks, we need to pay a lot for staging environment too even though we don't need many CPUs / RAMs.
We hope Atlas to support varied storage options in smaller cluster tier
1 vote -
Dump audit logs to log analytics workspace
Why can't we dump audit logs to log analytics workspace when we are using azure private endpoints to connect atlas
1 vote -
Introduce Serverless for AWS Frankfurt region
Company policy (speaking for a customer) requires data to be deployed in Frankfurt. Serverless would be very convenient to reduce pause/resume and scale-up times.
1 vote -
Investigation Buckets (dropdown menu) to enable predefined set of MongoDB & Hardware Metrics to investigate certain Data Layer SLAs
We have many metrics under "MongoDB Metrics" & "Hardware Metrics". User will have a good idea which metrics to enable while troubleshooting certain requirements.
E.g. User is investigating current lags in the data Layer. User has to select all the metrics that would help them get the data they are looking.
We can help the customer bit more by provide buckets like.
Options ( select one )
1. Investigate Lags
2. Investigate IOPS
3. Investigate Replication
4. Investigate Search Index
... and etc..This will pre-select certain metrics from list of Mongodb & Hardware metrics which will give them all…
1 vote -
Export mongo dump to AWS S3 Bucket
It would be good to have the ability to export mongodump's and mongoexport's files directly from Atlas to the S3 bucket. This kind of feature exists for backup snapshots. In our particular case, we want to delete a cluster but before that just export all data to S3. The backup snapshot takes about 1.6TB and mobgodump's file is around 650Gb. Of course, I can take a dump to my local machine and upload it to the S3 bucket. The problem is that my SSD is only 512GB on my laptop so it is impossible to export a full dump.
Thank…1 vote -
Need a Instance with unlimted storage .
We are seeking an instance with 2 vCPUs, 4 GB of memory, and a storage capacity of 500 GB.While we understand that the available M20 instance type supports the desired vCPU and memory specifications, we noticed that the maximum storage capacity for M20 instances is limited to 256 GB. Unfortunately, this falls short of our project's storage needs.
Considering this, we kindly request assistance in identifying an alternative instance type or solution that can meet our requirements for 2 vCPUs, 4 GB of memory, and a larger storage capacity of 500 GB. We would appreciate your guidance in selecting an…1 vote -
Reference existing third party integration in alert configuration notifications
Provide a mechanism that enables referencing an existing atlas third party integration when using the alert configuration resource to create or update a third party notification.
This is useful when a third party integration is imported or accessed through a data source, meaning the api token is not available. An example of this would be Slack integration as it has to be created through the Atlas UI using OAuth2, so the api token cannot be accessed in the terraform configuration.More details in: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/1074
1 vote
- Don't see your idea?