Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1242 results found
-
Credits API
I need an API that will allow access to the items under credits in the billing page.
This will allow me to pull this information daily into our master usage database to support our dashboards12 votes -
More functionalities in Collection (Data Explorer) Tab in Atlas UI
Here are some suggested functionalities
- Import and export of bulk documents.
- Quickly filter and sort the required documents. (This is achievable in Compass but not in Atlas UI)12 votes -
Extend / Configurable retention time of audit logs
This is a feature request to extend or have configurable retention time of audit logs more than 30 days in Atlas.
12 votes -
Add "Maintenance Completed" Alert Option & Activity Feed Item
There are existing alerts that will notify users when a Project Maintenance Window is "not needed"/"scheduled"/"started" but it would also be helpful to add an alert for when maintenance has been completed. This event currently appears in a project activity feed as "cluster update completed". This alert would help users who need to manually verify if any of their applications need to be restarted following maintenance events.
12 votes -
Export metrics to AWS Cloudwatch
Have an integration with AWS Cloudwatch to send the metrics from MongoDB Clusters to Cloudwatch so metrics and alarms can be setup in CW.
12 votes -
Customize CPU threshold for Autoscaling
Currently, to autoscale a cluster to the next tier, the "Average CPU Utilization must have exceeded 75% of available resources for the past hour."
Problem:
Some workloads remain near the 75% CPU threshold, given the nature of the workload. This can cause constant scaling events to occur which creates unnecessary noise.
We don't want to turn autoscale off because this is a beneficial feature to keep enabled on the cluster.
Solution:
We want to be able to configure the CPU % threshold for cluster tier scaling. For example, rather than 75%, we'd like the option to set the threshold to…
11 votes -
UUID Schema Validation
It would be very handy to have the ability to specify a schema validator using bson type UUID (binData subtype 4) instead of the more generic binData subtype 0.
11 votes -
Serverless instances on AWS Paris (eu-west-3) region
We are impatiently awaiting the arrival of serverless in France. A lot of projects are needed !
11 votes -
Disk queue length metric
Atlas exposes a few hardware metrics including Util% (presumably obtained from iostat or similar). However this metric is not very significant in the age of SSDs - a volume could be 100% utilized and still have spare capacity. A more useful storage-level metric is Average queue length - this is easier to interpret (high queue length = storage contention).
Would it be possible to add this metric to Atlas monitoring?
11 votes -
Allow db.killOp() and manual restarts on secondaries
Please allow us to kill user threads on Mongo secondaries. Sometimes we have long running queries on secondaries and need to kill those threads but can't do anything about it since we don't have admin privileges to kill threads.
Also please add the ability to manually restart secondaries, not just failover the primary.Thanks.
11 votes -
Allow option to configure default project_owner when creating projects through API key
We're currently using the Atlas Service Broker (https://github.com/mongodb/atlas-osb) which is built using the native Atlas REST APIs.
In the project creation, it creates the project using the POST /api/atlas/v1.0/groups endpoint via an API key. As a result, we have an unexpected user added as the project_owner of the project.
THis is due to:
IMPORTANTTo create a project using API Key credentials, you must specify an orgId. When you do, Atlas automatically selects the Owner of the specified organization with the earliest account creation date and time as the Project Owner for the newly created project.
The API…
11 votes -
Alert for backup policy changes
It would be great to have an alert that notifies you when someone edits the backup policies.
This would be good to validate and everyone to be aware of, because a bad change can cause major problems if it is necessary to restore a backup.
11 votes -
Graph connections per user (or per database)
Show a graph of connections per user.
It would be very useful to see how many connections each user has (or also, each db) over time.
It would allow us to see more clearly and faster which service uses how many connections.
11 votes -
Alerts based on Activity Feed - Rollback
Our main concern is 'Host experienced a rollback' is not an alert option!
Ideally, anything that shows up in the activity feed should be available as an alert.
11 votes -
Using Online Archive with Customer Encryption Keys
I'd like to use Online Archive but I need to use Encryption Keys that my company manages, not ones provided by MongoDB.
11 votes -
Profiler should only watch queries from certain users
It would be useful to provide the profiler an "allowlist" and "denylist" of users to watch queries from. Essentially, it is only useful to receive alerts and profiler reports for queries made by actual applications. It is not useful to have alerts show up for one-off queries made by a DB admin using a DB explorer.
11 votes -
billing
The billing invoice is split by project. If we have multiple team in the same project, it a puzzle. We need to bill by cluster in this case.
11 votes -
Being able to change the cluster name
a cluster has been in development for awhile .. but as new cluster are created within the project.. we'd like to change the cluster name ..
11 votes -
Rename Hardware Metric "Util %"
Under hardware metrics for a given replica set, there is a metric for "Util %". It is unclear on what this represents. After careful digging through the documentation, it appears to be a metric for Disk Bandwidth Utilization. I believe the metric name should be updated to reflect at least "Disk Util %", if not something more specific.
11 votes -
Show a graph of BANKED iops (AWS)
Atlas monitoring is great... but it would be super helpful to see a graph of banked iops. (or an approximation of this)
Suppose my iops limit is 100... and during the night my bank gets fully charged to 5.4MM.
During the heavy loads on my server, let's say my iops jump to a steady 500. This means that I am drawing 400 units from my bank. I can do this for 3.75 hours until my bank is exhausted.It would be so helpful to see an iops bank balance drawing down during peak, recharging during off-peak... and thus getting insight…
11 votes
- Don't see your idea?