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
-
Manage Feature Compatibility Version (FCV) flag separately from version upgrade
When performing a major server version upgrade (e.g. to MongoDB 7.0), Atlas automatically set the Feature Compatibility Version (FCV) flag to the same version.
We would like to see this be a two-step, i.e.
1. When upgrading to 7.0, Atlas keeps the FCV pinned at "6.0"
2. 1~2 weeks after upgrading, Atlas reminds us increase the FCV to "7.0", i.e. once we've seen it running stable.We had a major production-outage issue in upgrading to MongoDB 7.0 and because of the current Atlas FCV behavior we could not downgrade back to 6.0.
We understand that some users don't care about…
2 votes -
Change global default compressor setting
Hello,
I wanted to request a feature that would enable us to change the global default compressor setting ourselves? Something that could possibly be exposed on the Advanced Configuration settings page in Atlas? We're looking to re-compress our existing collections usingzstd
from the defaultsnappy
option and we want to create future collections using thezstd
block compressor automatically.Today, we have to create a support ticket and co-ordinate with them. It would be great if we could have this feature on the Atlas portal so that we can monitor the progress and trigger it whenever we want to…
2 votes -
Bulk explain() command
I want to be able to run the "explain" command for multiple database operations so that I can quickly estimate the RPUs and WPUs for my workload (instead of having to do it one by one for each operation).
2 votes -
tgw support for Atlas
Can you please provide TGW support for Atlas? We are using confluent.io kafka with TGW, and found ourselves caught up in situation where kafka has no direct access to atlas, both our EKS and kafka are directly connected to Kafka, but there's no way for kafka to access atlas, because EKS and atlas are connected over vpc peering. We do not take interest in PrivateLink. Our Kafka needs direct access to Atlas because we are running the mongo source connector. Only viable solution now is to run the mongo source connector on our EKS, which while works defeats the purpose…
2 votes -
Yearly backup option is required
We are planning to take backup yearly , but as of now available max monthly backup. If i want to take yearly backup need to take 12 months for single year which expensive , as per our audit team need 20 years back up retention then it is required 12X20 = 240 backups which is very expensive. If yearly backup is available only 20X1 = 20 only.
As of now only available below options:
Hourly
Daily
Weekly
MonthlyRaised case also in our support portal: 01198437
2 votes -
Migrate specific collection / database from a replica set to sharded cluster(not empty) without downtime.
It would be great if MongoDB has a tool to migrate specific collections/databases from a replica set to sharded cluster and vice versa. Migrating data with this tool should not cause any downtime in both source and destination clusters.
2 votes -
kill process for rolling index build from atlas
If index builds are rolling, then the Atlas console does not have the functionality to kill them if they take a longer time on a node. Is it possible to kill it like regular index creation from atlas UI instead raising a ticket to mongo
2 votes -
Suppres/Stop Alerts caused by Mirrored Reads
Sometimes the "Mirrored Reads" queries cause alerts of "Query targeting " to appear in Profiler. Since these queries are related to mongod process, we want to stop this type of alerts
2 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 -
Include IdP Group and Atlas Role mapped in the ROLE_MAPPING_CREATED event
When an Atlas Role is mapped to an IdP group in the Federation Management Console, an event is created with the eventTypeName "ROLEMAPPINGCREATED" and the description "A Role Mapping was Created". The event returns in both the Atlas Admin API events endpoint and the Organization Alerts. It would be beneficial for auditing to include the IdP group and Atlas Role in the event.
2 votes -
More documentation about alert
It would be great if there were a doc explaning what each Alert Event Types means (and even that could give us some examples). And the same documentation should explain wich alerts have thresholdconfig or metricthreshold_config.
The documentation that I have found with a little explanation is thw below (and it shows some alerts type that don´t work)
Example: OPLOGBEHIND => When trying to use this one on terraform, it returns an error saying it does not exist (the one that works is: REPLICATIONOPLOGWINDOWRUNNING_OUT)https://www.mongodb.com/docs/ops-manager/current/reference/alert-types/#user
2 votes -
API KEY - Restrict by Database
Since Mongodb Clients cannot be used in Edge Runtimes (like Vercel, Cloudflare, etc.) the user of Data API becomes inevitable. The Data API access should have same features like user roles where we can restrict an API KEY or an ENDPOINT to have acccess to a single database or multiple database.
2 votes -
Terraform data source for Point in Time Recovery
It has been confirmed by MongoDB support, that in Atlas, there is no way to know the last point in time you can recover a cluster to using OpsLogs. Surely this is an oversight, as we should be able to tell, from the backup material available, what point in time we can recover to, and not just from.
I need to automate a restoration of a cluster into another cluster in another project in a second region. I copy backup material, including OpsLogs, to that region. I would like to be able to use Terraform to get the Unix Timestamp,…
2 votes -
Allow turning off backups on serverless and free instances
We have a use case where we would have liked to use a serverless instance but cannot since we cannot disable backups on serverless instances.
We can't enable backups on this specific instance because of data retention restrictions so being able to turn them off completely on serverless and free instances would be ideal.
2 votes -
Enhanced Access to Secrets in the context.environment Object
We would like to see an improvement where secrets can be accessed as environment variables directly through the context.environment object. For example, if we have a secret called myApiKey, we would like to be able to access it in a function using context.environment.secrets.myApiKey.
This would make the process of storing and accessing environment-specific sensitive data like API keys, access tokens, etc., much more straightforward and error-proof.
As it stands, we're creating a workaround by saving env specific API keys as secrets, and then using some logic with context.environment.tag to fetch the correct environment API key. However, this approach is not…
2 votes -
Include more actionable data in Alert emails
Currently the alert emails just link to the profiler page with nothing selected. This makes it guess work if there are multiple items in the profiler to examine. If you are unable to check the profiler within 24 hours of the email, no data could exist specifically for the alert email.
It would be much more actionable if the email alerts mentioned the collection that was being queried, the appName that triggered the query, and a direct link to the query in the profiler showing complete details of the query that triggered the alert.
This would make triage near instant…
2 votes -
Existing Owner business
Please SOLVE my billing
2 votes -
dynamic auto-downscale (configurable)
MongoDB have automatic fixed limit for auto-downscale (50%) but sometimes is neccessary downscale with other amount, ie: in our case in the night the clusters have 55%, 60%... will be productive for us that the % limit for downscale will be parametrizable.
If I configure 60% I know that all the nights the cluster auto-downscale to previus instance.2 votes
- Don't see your idea?