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
-
Credits by period
Provide the ability to display and export credits by period (from date - to date) instead of selecting each single month, so that uers can easily display credit trends, etc. without downloading a lot of cvs and merge them togheter.
2 votes -
alert
While setting up alert allow additional text to be added. This would help to write SOP for action needed on such alert
2 votes -
Scheduler for Aggregations that runs for more than 90 seconds
A online Atlas service, where you can upload/write your aggregation and then schedule the aggregation to run. It should allow for aggregations that might run for a few hours.
2 votes -
"Native" Azure integration (Costing, Resource Groups)
I would love to do away with MongoDB CosmosDB on Azure - simply because
a) CosmosDB emulator is troublesome to install (for local development)
b) Limited MongoDB feature support
c) Difficulty getting Bulk inserts/upserts to work well in CosmosDB MongoDB (due to rate limiting and bugs with IsUpsert=true)Currently we have 18 CosmosDB databases - nfortunately, the main barrier of entry for my organization in adopting Atlas is it's Azure integration - specifically:
a) Atlas resources are not visible/manageable via Azure Resource Groups - this makes our existing Azure DevOps practices/infrastructure as code obsolete for this (versus all our other…2 votes -
Add a Transaction Commits / Sec Metric Graph to Atlas
Add a graph in Atlas to display "transactions.totalCommitted" on a per second basis to the Atlas metrics UI. Customers that are using transactions are often more interested in the # of transaction commits per second than opcounters.
I have had to use mongostat on a number customer evaluations because this metric is not available.
2 votes -
Allow to resend alert to a PagerDuty service
Like with other type of alert targets (Send to), we would like to be able to resend an alert to PagerDuty.
The reason is that an alert sent to PagerDuty can be mistakenly resolved but the real issue is still there, and the alert is still firing in Atlas.
Because it is already firing, it won't fire again so from that moment on, there is no way to get a notification of that alert so we might be missing a real issue.
2 votes -
Helpful error message when restoring backup
When I recently attempted to restore a db backup I got a cryptic error message stating "Error: Cluster Not Found"--which was extremely confusing considering that I pressed the restore button in the backup options. After some great tech support, I added my user as project owner and everything worked fine.
Please make the error message clearer in both the Restore and Download backup scenarios.
2 votes -
Precautionary Change/Recommendations for Shard Drops
If a user submits a configuration change to drop a shard, Atlas will sift through the cluster metrics and advise any necessary changes needed in order to complete the change without any errors/delays. For example, it will share the correct number of IOPS/cluster tier that needs to be used since the workload to drain a shard will increase; as well as other precautionary measures that should happen prior to dropping the shard (i.e. balancer needs to be turned on, etc).
2 votes -
Better message for "Removed Indexes" in Activity Feed during Atlas rolling index build
During a rolling index build, it is expected to have 2 "Deployment configuration published" notifications - 1 for Added Indexes and another 1 for Removed Indexes. This is because an entry for this desired index is added to the automation config and then the automation agent builds it accordingly. Once the agent is done building it, we remove the entry for that index from the automation config. Indeed, this does not drop the index.
However, from the term of "Removed Indexes", it can cause confusion that the index is dropped. Hence, this feature request is filed for clearer message so…
2 votes -
Add Alert for outdated Agents
Add an alert type for outdated agents
2 votes -
Identification and labelling of MongoDB connections
It'd be REALLY useful if there was an ability to provide a label (basically a string) when creating a new connection to MongoDB from an application, to say where the connection is coming from.
For example we use a bunch of microservices and each API sets up a new connection. It'd be very useful to be able to see how many connections each API has at any given point, as it'd allow us to determine if the microservice is misbehaving with the database etc.
2 votes -
Add visual information to indicate if a collection is capped or not.
Right now there is no way to tell through the portal or Compass if a collection is capped or not. It would be helpful if there were some visual indicator in the Data Explorer if a collection is capped and if so what the retention parameters (bytes and max documents) are set to.
2 votes -
Implement a refresh button for the BI Connector in Atlas
When changes, such as when collections are added or removed, occur to an existing database with BI Connector enabled, the BI Connector needs to be cycled off and then on. This process is not well explained for Atlas. I feel that a refresh button that ripples Bi Connector in Atlas when changes occur would be beneficial, rather than having to dive in to edit configurations --> slide the "enable bi connector" from off, wait, than back to on.
2 votes -
Show node region on the metrics tab
It would be really useful if the Atlas Metrics tab showed the node name and geographic location similar to how the Cluster Overview tab shows the node's region. In this use case, we have nodes located all over the world, so its useful to know where a node is located when reviewing it's metrics.
2 votes -
Azure Stack Support
Many of us have a requirement to host our databases in countries without an AWS, GCP or Azure data center.
Azure Stack is a hybrid cloud solution that allows vendors to use Azure in their local data centers using the same APIs. MongoDB atlas support for this would be immensely valuable.
2 votes -
Expo support
It would be great if we could use "MongoDB Realm" with Expo (expo.io).
I understand that the React Native SDK would be hard to integrate therefore the Web SDK for MongoDB Realm would be the ideal integration choice.
Many people use Firebase/Firestore's Web SDK with Expo, enabling the MongoDB Realm Web SDK to work with Expo in the same way would allow many Expo apps to use MongoDB Realm.
2 votes -
Have live tool migration re-establish connectivity with on-prem cluster in case of connection failures
While trying out Live Migration tool for data transfer from our on-prem cluster to Atlas, we had an issue where Atlas ran into connectivity issues with the on-prem cluster with respect to Live Migration tool. As the tool couldn't re-establish connectivity with on-prem cluster, we had to cancel migration and initiate data sync all over again. While this is fine for a small cluster, this can't be feasible for a large PROD cluster where we have 20+ shards and with data volume in order of 40-50TB compressed size.
So, even if there is a network disconnect or any maintenance happening…
2 votes -
Clarify Python vs PyMongo
When connecting to a Atlas cluster and selecting to connect via a Application you can select to connect with what "Driver" where you can select "Python".
For new users, they might think that the Python library (https://www.python.org/doc/versions/) is what is being referenced when in reality Atlas is referring to the PyMongo Driver.
For clarity, alter the UI from "Python" to "PyMongo" or "Python (PyMongo)" or something similar to differentiate between Python and PyMongo.
2 votes -
private link - common dns suffix
when creating a private link, the resulted dns for the cluster is in the form of "cluster-pl-.{somerandomstring}.mongodb.net"
the only difference from the public endpoint is the 'pl' addition in the first section.in order to configure the vpn wildcards and rules,
it can be extremely helpful to have this separation more general, for example
cluster.{randomstring}.pl.mongodb.net -- private links
cluster.{randomstring}.mongodb.net -- publicthat way we can use the wild card *.pl.mongodb.net to differentiate and route the traffic accordingly
2 votes -
Disk Usage Breakdown
When looking at the cluster page, I can see Disk Usage = 1.6GB, for example, but I don't know what the breakdown of that is. For instance, if I look at the same DB and add up the size of the collections themselves it's barely 1.5MB. So 1.6 Gig disk = 1.5 Meg data. I suspect this is oplog etc. but it is a pretty confusing potential red herring when diagnosing performance issues etc.
2 votes
.png){kind=link}
- Don't see your idea?