Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1362 results found
-
Have EventBridge send an error message to Atlas to stop flow of Trigger data at the source
Currently, once a Mongo Trigger makes a successful hand-off to EventBridge, it doesn't have insight into EventBridge issues landing the data in its destination. Currently, you have to set up separate code to process failed EventBridge events using the DeadLetter queue. You also need to set up a process to integrate this data from the DeadLetter queue back into the EventBridge destination. If the requested functionality existed, you would only need the Trigger restart process to handle any failure in the data stream from Mongo to EventBridge destination. This will also enable a single place to monitor the data stream.
1 vote -
invoice
Invoice should show the ClusterName combined with Cluster Tier and Server Hours same with Data Transfer. With these, it is easy to determine how much cost we are spending per ClusterName. Right now it only shows per ClusterTier which is hard to separate the cost if you have 2 same ClusterTier.
5 votes -
Administration API Auditing
Looking for more verbose and central auditing of Administration API key usage. Currently, not all actions are logged to the activity feed.
We understand we can refer to the Access Control List for the API key and get date/time for last usage, but, we would like to have visibility into endpoint, action, last used, etc. for each usage of the key.
15 votes -
Allow --removeAutoIndexId option to Atlas live migration as default
Apparently Atlas live migration does not support --removeAutoIndexId option due to which some collections having
autoIndexId set to falsedoes not allow live migration to work successfully. Please add --removeAutoIndexId option to live migration.1 vote -
Add support for HTTP based scraping without IP restriction
Prometheus supports a lot in the HTTP scraping space, including oauth and Bearer token based scrape targets.
Currently we use Grafana cloud that has a list of IP address that can scrape from. This "can" change, and if it does and we hardcode this access into Atlas based on IP then it will break the scrape.
Could Mongo add support for token/oauth based scraping. Where we provide these tokens in a HTTPS call?
I think this would solve the issues with things like private link, or peered network connections. It would also allow "any" prometheus server that can make outbound…
3 votes -
Cache last aggregation query for each collection
For each collection – on the aggregation tab, cache the last query which was run – keep it pre-populated in the textboxes.
It’s so easy to accidentally click away from this page and when you come back, having to start from scratch always takes a bit. Ideally I want to be able to leave this view and come back as though nothing had changed.
1 vote -
Re-run a query from the profiler tab
When using the profiler tab, if there is a $regex expression specified, it comes back in the logs as $regularExpression. Similar issues for ObjectID() vs generated $oid.
For some reason, you can’t take the query the profiler outputs and just plug it back in to mongo. You have to manipulate it.
Displaying a valid query from the profiler tab in which I could either click “Open query in aggregation viewer” and open the aggregation pane for that collection with this query pre-populated, and/ allow easy copy+pasting of a valid query elsewhere.
The first thing I've been doing with query optimization…
1 vote -
1 vote
-
Show queries that exceeded maxTimeMs in the Atlas Profiler
We had some queries hit the maxTimeMS and fail. We had to download the log files for visibility into those errors. That is info that we would love to see in the Profiler!
2 votes -
Recommendation to the change the tier cluster
Based on CPU and memory usage metrics over a certain period of time, a recommendation could be made to change the cluster tier to a higher or lower one (inform which cluster it would be recommended to change to) and notify through some channel, such as eg email/slack.
5 votes -
View TOP N queries per CPU / memory / disk and number of execution for each query.
This type of metric is common in relational databases and I think it's important to deploy in the Atlas interface.
Top queries by CPU/memory and disk over a period of time or real time. It is important to have this visibility and improve the respective query(s).
It is good to know how many times each query was executed during the respective analyzed period.
3 votes -
Feedback and public roadmap.
I have voted and written since 2020 several improvement ideas for your platform.
Being a client for a major insurance company, I'm disappointed to see that for several suggestions dating back more than 12 months, it doesn't even seem to have been looked at by your team.
It would be more than interesting to have an idea for your roadmap as well as a dynamic management of the catalog of ideas (feedback) maintained by your customers.
I consider this a lack of respect for your users and customers.
Some examples:
https://feedback.mongodb.com/forums/924145-atlas/suggestions/40638277-atlas-backup-to-second-region
https://feedback.mongodb.com/forums/924145-atlas/suggestions/43289796-max-database-users-not-visible
https://feedback.mongodb.com/forums/924145-atlas/suggestions/42163234-authentication-on-azure-iam
3 votes -
API for Granting Infrastructure Access to MongoDB Support for 24 Hours
As per documentation at https://www.mongodb.com/docs/atlas/security-restrict-support-access/#grant-infrastructure-access-to-mongodb-support-for-24-hours one can grant access for support for 24h only via the UI. It would be very useful to be able to do this via the Atlas API.
1 vote -
Warn when attempting to add a new IP address to network access that is already covered by an existing entry
Currently, if one tries to add a new IP address to the list of whitelisted IPs for a database in the 'Network Access' page, and the new IP is a duplicate of an existing entry, there is no warning or indication given to the user, and the list of IPs remains unchanged.
This makes it seem like the button to add a new IP doesn't work, as the list of IPs doesn't change.
So there should be some indication that the user attempted to add a duplicate IP, and because of that, the list of allowed IPs was not changed.
1 vote -
Reshard Global Writes Collections
MongoDB supports resharding, so not being able to change the global writes shard configuration is very strange. It makes it impossible to fix mistakes with the shard configuration. Even if it requires blocking to redo or remove the shard configuration it should be possible.
2 votes -
Please clean your mind
What i mean is for newbie mongodb is trash , I am full stack dev and i have to use this for complete mern project and how we gonna do that => by watching video tut which you guys but you guys change syntax every year that makes impossible to work on ongoing project.
So I somehow arranged to have mongodb in my mac m1 then bloody xcode did some changes now again errors after error .
So I somehow thought I should use atlas atleast i will not be in my system and guess what you guys changed some…1 vote -
Expose Locking Metrics
One of our customers have asked if we can expose locking metrics through the Atlas UI to assist with investigating suspected lock contention issues.
We have this information in FTDC and our customer feels it would be helpful for them to have this information too.
6 votes -
Having the alert "Acknowledge for" option actually do acknowledge the alert for the specified time period
I gathered that Atlas alerts are design to retrigger once the condition is met. Then what does acknowledge mean in that case when providing any timeframe like forever? To me acknowledging an alert forever means that the alert would never to raise again.
In our case the number of connections for one cluster out of many goes slightly over the threshold, then shortly thereafter, goes below the threshold . The condition is 'flapping'. I know that this connection count condition is not leading to the number of connections to be exceeded. But, I don't want to ignore that alerts for…
2 votes -
Trigger runtime is US by default which is not GDPR compliant for EU countries
The ATLAS Trigger UI should let the user select the region for the realm deployment done in the background. At the moment it's not fair because (1) at no moment you're noticed the runtime will be in the US (and for UE countries it matters a lot, it's not GDPR compliant) and (2) it makes the nice ATLAS Trigger UI useless for UE countries...
We're forced to create a realm app manually to be able to select a local deployment. We appreciated the 'trigger' section on the ATLAS side. It's more integrated and makes following trigger operations easier. Now trigger…
1 vote -
$lookup available cross-db
Hi,
it would be a great feature to be able to use $lookup cross-DB
thanks,
1 vote
- Don't see your idea?