Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1262 results found
-
The page fault metric is not available in the Datadog integration
The page fault metric is not available in the Datadog integration
3 votes -
Real Time data explorer
I would like to see documents inserted into the database in a shell show up on the cloud data explorer UI in real time without refreshing the screen.
3 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 -
Show index name/details when creating or dropping index via Data Explorer
When Atlas user creates a rolling index in Data Explorer, we can see the name of the index being built in Activity Feed. However, if Atlas user creates an index or drops an index, the index name is not revealed in Activity Feed. This creates some complexity to trace which index is created or dropped via the Data Explorer
1 vote -
Force restart of unhealthy node
Right now, there's a "test failover" option, which shuts down the primary and forces an election. However, the option is only available if the cluster is in a healthy state.
If, for whatever reason, the cluster is unhealthy, it's impossible to manually restart the primary. It should be possible to force an election in an unhealthy state. Often, this is all that is required to get back into a healthy state (e.g. if the primary is in a CPU burning loop that was caused by an unexpected write pattern that has stopped.)
103 votes -
Trigger event when user confirmation state change
I suggest that after user registered they should ve able to log in regardless of his account confirmation state, but if he is in a pending state, he could not do any read/write operation unless his own user data and his own user extra data,
And the user can also detect if his confirmation state is change
1 vote -
Expose the killOp() action when creating custom roles in Atlas UI
It would be nice to have the
killOp()action exposed when creating a custom role in Atlas.I also think it would make sense to grant this action to the
atlasAdminrole, but at a minimum I feel that Project Owners should be able to create a custom role that is allowed to kill ops that were initiated by other database users.16 votes -
It would be great to have a tool with historical data about database and collection.
It would be great to have a function where we can , using only atlas interface to filter a month and a year , and we cann see historical data about sizes.
3 votes -
Add Alert for outdated Agents
Add an alert type for outdated agents
2 votes -
invoice should show support costs under project and not organization
We need the support costs (in our case Atlas Pro) to show up for each cluster under the project on the invoice. Right now, it shows up as a separate line item in a lump sum under the organization. It makes it difficult or impossible to properly bill the individual cost centers for support costs for their clusters.
If those costs showed up next to the clusters within the project, it would be easy to say project1 goes to cost center 1, but now we have to do project 1 goes to cost center 1 plus some percentage of the…
4 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 -
Allow more aggressive downscaling of clusters
Autoscaling clusters down a tier doesn't seem to work very well. Even under rather low memory usage, it doesn't seem like the procedure really ever triggers.
8 votes -
Add alerts on disk IOPS and CPU IOWAIT %
To help catch heavy disk workloads before they become problematic, it would be great to have alerts on:
- disk IOPS percentage utilization for disks without burstable IOPS
- burst credit utilization for disks with burstable IOPS
- CPU IOWAIT %70 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 -
Permission level to query snapshots
Right now I have to give an admin permission to allow someone on my team to query snapshots from a backup (i.e. downloading the tunnel file).
I don't want to give an admin permission just to allow our data analysts or a developer trying to understand data corruptions to view the database at an older date.3 votes -
Add Elastic integration to Atlas
Add support to send cluster metrics to Elastic. Elastic has recently been putting a lot of work into their APM and logging solution, this is now a viable alternative to NewRelic and Datadog and is gaining traction. It would be great if Atlas supported sending metrics to Elastic. Please see below for references
https://www.elastic.co/apm
https://www.elastic.co/siemThe use case for this is the same as NewRelic or Datadog. I wish to monitor my Atlas clusters from inside Elastic, create dashboards and set up alerting
22 votes -
Have the ability to downgrade
Currently Atlas doesn't support the ability to downgrade major version. I know with Ops Manager on-prem you can do that, which is helpful if you find issues during an upgrade. Would it be possible to get the ability to downgrade one major version on the roadmap?
As of today, if we have issues with an upgrade, we have to build a new cluster with the older version, export and import into the new cluster. That's a much more painful process including the fact that you have to change the connection strings of your applications to point to the new cluster…
10 votes -
Ability to search for filter conditions in Atlas Alert builder
It would be helpful to be able to search for a trigger condition in the Alert builder when creating/editing an alert.
Currently, you need to scroll to find specific conditions, but the list is long so it can take some time to find the particular one needed.
4 votes -
Save common collection filter/query
As an ex-mLab customer, I used to really enjoy having common queries on collections saved, like "find a customer", "list latest X" etc Is a dropdown with a name and the query, so when you select it you can quickly perform the search.
5 votes
- Don't see your idea?