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
-
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 -
CDC
Wanted to have the CDC information stored as json or parquet in a bucket storage for retrieval at a later point to understand the data transformations that has happened in our Application Transactional collections.
2 votes -
Ability to quickly filter backup activity from the project activity feed
The activity feed is often clogged with backup activities. It would be extremely useful to be able to quickly filter out the common 4 or 5 project activities that are related to a backup snapshot being taken.
2 votes -
Please let users know you will be making huge charges for no services provided!
Please let know users that Atlas will generate huge charges for NO usage and will be hit with huge bills without having even used your service. Also, please let users know that MongoDB will not build or compile on Raspberry Pi either Ubuntu or Debian!
2 votes -
Disable duplicate linked Organization names
Currently, one can create multiple linked sub-organizations under a main billing organization, but having the exact same names. The below API command, run repeatedly, will create the same sub-org name with different orgId's. I believe this only serves to confuse administrators and makes management more difficult -- therefore, I'd rather have the API fail with "HTTP 4xx: Another organization already exists with the same name."
curl -s -X POST --digest -u "$ATLASPUBLICKEY:$ATLASPRIVATEKEY" \
--header "Content-Type: application/json" \
--data '{ "name": "MYORG", "orgOwnerId": "MYORGOWNERID" }' "https://cloud.mongodb.com/api/atlas/v1.0/orgs" \
| jq -r .organization.name2 votes -
mTLS for Atlas Alert Webhook Integration
Atlas currently does not support mTLS on HTTPS traffic to Alert webhooks. Some customers whose alerting services are on-premises may require this per their security policy. We should support mTLS on webhook integrations to enable those customers to use their on-premises alerting systems.
2 votes -
Add a button to retry to collect a payment on the billing - invoices tab
Add a button to retry to collect the payment from a credit card on user request. This will help when there are problems with the credit card funds or credit limit.
2 votes -
Atlas triggers on serverless instance
Atlas triggers on serverless instance
Hello, Atlas triggers would be a really nice to have feature on serverless instances.
2 votes -
U domain Verification
If you are able to verify the parent domain for your company, then you shouldn't need to have to verify the sub-domains associated with that domain. Company's do not generally advertise their internal u-domains on the internet therefore any verification on that sub-domain will naturally fail. This is hindering us from integrating our Okta credentials with our login information.
2 votes -
Feature: Atlas UI -- Star/Favorite/Bookmark of Project
It would be nice to be able to star/bookmark projects, so I don't have to type half the project name in every time I switch between environments--eg. like in Datadog, star a dash board and it shows up at the top of the list/without search
2 votes -
Add EventBridge integration for Serverless instances
Currently EventBridge integration doesn't work for serverless instances
2 votes -
Support exporting Custom routes
Supporting export of custom routes with peering connection (with GCP in our case). At this point it's not possible to access atlas from our on-prem network with -priv FQDN, we would have to use the public ones by managing source ip in GCP firewall (painful on a remote workers world) or adding a Google Cloud VPN product to create some kind of vpn connection. Just permitting export of private subnets would be great !
We have peering with other product and they support it !2 votes -
Approval workflow for database deletion
The current Termination Protection only prevents accidental deletion of a cluster. It helps to have a similar protection to databases inside the cluster.
Even better if there is an approval workflow, in which several people must accept before a database/cluster is deleted.
2 votes -
Restore indexes from AWS S3 snapshot.
While working with export snapshot to AWS S3, I found there is no way to restore indexes from metadata.json, along with data there must be opportunity to restore indexes as well otherwise have to rely on custom solutions and this may include external dependencies.
2 votes -
Send alert(email) when database is deleted
The alert conditions do not contain conditions like
- when database is deleted
- when cluster is deleted
- when project is deletedWe want to get notified if a malicious person or someone by mistake deleted major parts of the database.
This simple notification is not possible right now.2 votes -
Add hint support for MongoDB API functions
The "hint" option for Mongo Shell query/write operations is very useful when the Query Planner does not select the right index by default, or just to make sure the right index is used. When you cannot use the "Hide index" feature on the index selected by default, "hint" becomes the only way to have an efficient IXSCAN.
However, the "hint" feature does not exist on the MongoDB API functions (https://www.mongodb.com/docs/atlas/app-services/functions/mongodb/api/). This means that no command we can run inside a Trigger can specify a "hint" option.
I think that "hint" is a great "backup" feature for cases where…
2 votes -
Accept VPC peering connection when created by MongoDB::Atlas::NetworkPeering
VPC peering connection created by CloudFormation resource
MongoDB::Atlas::NetworkPeeringhave to accepted in AWS, using GUI, CLI etc. Would that be possible to get this done using CF only?2 votes -
Use additional metadata to differentiate processes
Right now Ops Manager monitoring identifies MongoDB processes according to hostname:port. Unfortunately, if 2 processes have the same short hostname & port in the same Ops Manager project, they'll be treated the same even if they are actually different processes with different FQDN.
Please either allow the use of additional characteristics (FQDN, replica set name, config server name, etc) for differentiating MongoDB processes or provide some way to tag 2 or more processes so monitoring doesn't accidentally miscategorize them as the same process.
2 votes -
Query Online Archive over Web UI
There is currently no possibilty to query a collection of an Online Archive via the Web UI of Atlas. This is only possible for the "normal" collections.
It would be great if it would be possible to also query Online Archivce collections similar.This is related to the request of https://feedback.mongodb.com/forums/924277-data-federation-and-data-lake/suggestions/40949902-access-online-archive-in-customer-data-lake
2 votes
- Don't see your idea?