Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1415 results found
-
Console to see what's actually happening
My cluster operations is at 100 and i don't know what's causing that. I would appreciate having a console to see what are those operations
1 vote -
Metrics Collection
Any way could analyze and store all the queries we have made
Fields would be: execution time, IO, cpu usage, etc...
This collection would store only 1 or 2 months of data.1 vote -
Atlas console authentication logs
MongoDB Atlas does not seem to provide a tool or a page that will show the authentication logs for the Atlas console users. Example - a log indicating when a project owner or a cluster manager logged in or out of the Atlas console along with the relevant time stamps.
I have raised a support case with MongoDB and the engineer suggested to raise a feature request as this feature is currently not available. Refer case #00755619.
Thank you.
1 vote -
Role to work with vpc peering with READ ONLY access for rest in the Atlas Dashboard
The requirement is:-
An individual will be able to see (READ ONLY access) the Metrics. He/She will be able to work (Add/Delete) with Network VPC Peering.1 vote -
Support of new EBS Volume type (gp3)
When creating cluster , We have not option to select GP3/GP2. while newly introduce gp3 EBS volume have less price and high IOPS.
So why we need to settle for less.
1 vote -
Page title says "Create Cluster" when editing cluster config
Small thing I just noticed (confused me for a second because I had a second tab open to actually create a new cluster). My idea is to have the the title say "Edit Cluster" instead.
1 vote -
NodeJS Trigger Dependencies
I'd like to have NodeJS dependencies (e.g. the AWS NodeJS SDK) available in my Atlas triggers.
1 vote -
Option to take a Cloud Backup snapshot on destination cluster before restoring if Cloud Backup is enabled on it
An option should be provided to allow a user to take a snapshot of the destination cluster of a Cloud Backup restore before the restore is performed so that they can easily "revert" the restore if they need to (by just requesting a restore using the snapshot that was taken just prior).
It's possible to be in a situation where you've selected an incorrect snapshot for restoring or that you'd supplied the incorrect cluster for the snapshot to occur (this is less likely to happen in the UI than it is to happen programmatically via the API). Taking a snapshot…
1 vote -
Allow transactionLifetimeLimitSeconds to be modified from Atlas
We need to be increasing the default value of transactionLifetimeLimitSeconds to larger numbers (usually 300 instead of default 60). Considering number of clusters we running / we are going to be spinning up in the future its cumbersome to keep requesting this change from support. Instead please allow us to set or modify this from the Atlas GUI.
1 vote -
Include Username in Profile page
The profile page would be more use if the listing included the username so you could work out which application was making the queries.
1 vote -
Provide insight to slow queries on shared instances (like M5)
Currently, features to give insight to slow/optimisable queries are only supported on non-shared instances (i.e. M10+). Would like to see this for shared instances too.
On a side note, this was possible in the cheaper mlab.com setup, which was forced into Atlas.
1 vote -
Ideally migration of terraform state should be handled or provide a tool for migrating state
Hello,
We initially rolled out all our clusters with mongo atlas terraform provider version 0.7.0. Since we hadn't pinned the version, we started seeing warning listed below in the terraform plan.Updating as indicated based on the warning means, a deletion and recreation of the private endpoint/link related resources which will lead to downtime as the cluster will be inaccessible while the private endpoint/link is being recreated.
Ideally migration of terraform state should be handled or provide a tool for migrating state so the resource can be migrated without recreation.
============================================
There are warnings related to your configuration. If no…
1 vote -
Correct DNS lookup with cross-region peering connection
A cross-region peering connection, say from an Atlas cluster in us-east-1 to some application running in eu-west-1, should allow the application to connect to the Atlas cluster through the peering connection. However, the DNS names of the cluster, e.g. my-cluster-shard-00-00.abx.mongodb.net, resolve to the public IP address of the cluster's node when looked up in eu-west-1. As a result, the application doesn't route the connection through the peering connection but rather tries to route it through the public Internet.
The solution is to manually find the private IP of each mongo node, and add an entry in /etc/hosts for each. This…
1 vote -
Number of times particular index used in last 24 hours.
It is really helpful to get use of indexes in numbers in last 24 hours to eastimate the use of particular index.
1 vote -
code
can you make it so that you can connect from mongodb like you would in mongoose
1 vote -
Include security group and tag for privateLink setup
On the Private Endpoint (and VPC Peering) setup screen in Atlas, present options to:
- include or modify "security group"
- attach a "tag = name"
That way when user has the AWS CLI command generated, it includes security & tag
1 vote -
if we had option for diabling javascript execution on database we would have to no worry about it
javascript excuiton can be used for harm and mass deletion data. İf we had no javascript execution we would be safer.
1 vote -
Change write concern on the Atlas Clusters
Atlas does not currently allow to change the default write concern at the cluster level.
It it necessary to have a possibility to change it in order to avoid or minimize rollbackfiles during failover.
1 vote -
Zabbix integration
It would be interesting, Atlas could also be monitored via SNMP, in order to be monitored by Zabbix.
Many companies have their own CommandCenter, where they centralize monitoring in a single tool.
1 vote -
Show hardware stats like CPU, System Memory in Metrics single-node view
Currently, some hardware metrics charts like Normalized System CPU are only available in Metrics when viewing the replica set (multiple nodes).
But if you click on one node to see metrics for that server alone, the hardware metrics do not appear in the available charts.
This is confusing -- it'd be helpful if the same metrics plots, including hardware metrics, were shown in all Metrics views.
It's possible to remove some nodes from the "replica set" view by unchecking them in the Toggle Members boxes at the top of the screen, but that will now allow you to view charts…
1 vote
- Don't see your idea?