Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
169 results found
-
Make AWS EBS Burst Balance metrics available in Atlas UI
Make EBS Burst Balance Metrics available within the Atlas UI. Currently it is not easy to 100% understand how much burst credits are being used and whether they have actually been depleted.
You can infer it from the IOPS metrics going above baseline IOPS and then suddenly dropping down but would be better to see the balance itself to be 100% sure. This will save support requests to do so.13 votes -
Change Atlas Metric Timeline Annotations Color
Filing this on behalf of customers that are having a hard time telling orange and brown apart in Atlas metric timeline annotations (node become secondary, node becomes primary)
1 vote -
3rd Party Hooks
Within Atlas today, we have a number of channel options to send alerts (Ex. OpsGenie, Slack, VictorOps).
I would like to see a hook integration provided by Atlas so any tool can recieve alerts from their cluster. Ex. I can recieve my cluster alert in Microsoft Teams.
3rd party hooks can increase the stickiness of Atlas and improve freedoms for teams and their existing toolsets.
3 votes -
Show total disk size and index size used for each cluster prominently so we can upgrade if we need to
Right now, I do this manually. Would be good to see the totals prominently, along with a recommended upgrade/ not next to it, and single click to select the next size.
1 vote -
Data Transfer Limit
since as documented there are limitation on network traffic in M0/M2/M5 instances, it is mandatory to have a metrics/alerts (also for free ones) to monitor this value in a 7d sliding window
9 votes -
Display chart annotations more conspicuously
To access chart annotations, users have to first hover over the metrics display, click on the info icon next to the title of a specific metric, and then read the annotations under the explanation of that metric. I didn't know they even existed until a support person happened to mention the vertical lines and I asked what they were. It would be more user-friendly to have the annotations (really, a legend for vertical lines) displayed separately in a more conspicuous location. Maybe in an info icon next to the annotation toggle? Another option would be for the vertical lines to…
1 vote -
Mongodb atlas logs - IP whitelist information
Hi Team,
We understand that network whitelist information (IPs added/removed) will be available only in portal under project activity feed. As our requirement is to access this information via API.Please let us know is there any feasibility of having these project level network whitelist information through API or in db logs in near future.
1 vote -
Add full screen mode for multi-graph Metrics and Status views
Unless I've missed a button somewhere, it would be nice if the "Metrics" tab for clusters and "Status" tab for shards had an option for expanding the entire tiled graph view into a full screen view. We have some TVs around our dev pod where we display these graphs and it would be great to see several graphs at once in full screen view.
2 votes -
Improve "Host has index suggestions"" alert by including the hostname
The "Host has index suggestions" alert notification does not contain any reference to the host/deployment that triggered it making it hard to figure out where it came from. A hostname reference would be very helpful.
5 votes -
Custom replica set tags
Currently Atlas comes with pre-defined Replica set tags such as Provider, Node Types, Region.. But as of now no options for user-defined tags.
Please provide options for custom/user-defined replica set tags.5 votes -
Make RSS feed entries more consistent
We would like to consume your status RSS feed to help us programmatically warn our internal groups when you have issues in a given region. One problem that we see with this is that the messages that we have seen posted are pretty inconsistent with how they specify regions. Examples: Oregon (us-west-2), AWS EU-WEST-2, AWS Sao Paulo. It would be very helpful to us, and probably your other customers as well, if the messages were more consistent in how they reference AWS regions.
4 votes -
Manually replace / restart virtual machine
Allow to replace / restart the underlying virtual machine of a node.
Sometimes this is all that is needed to get a cluster out of an unhealthy state. Currently, only support seem to be able to do this.
3 votes -
Allow bulk changes to alerts - e.g. changing slack channel
Changes alerts is really painful. For one thing, pressing the Enter key doesn't close the dialog and nor does pressing Escape.
This makes it really painful to change something simple like the slack channel used for alerts.
2 votes -
Add a monitoring that always shows the current primary
When there's an election and the primary changes, it's hard to get a good view on how does the primary functions in a macro fashion.
Please add a monitoring column (or an equivalent solution) that can show the monitoring information for the primary at the time, so I could look at the past month or so, and see how does the primary performed, even if it was a different server every time.This will make it much easier to understand various actions we take like changing indexes, improving queries, upgrading the database version, upgrading the driver, etc.
4 votes -
Disk throughput in monitoring
Currently we have disk IOPS in monitoring (both read and write).
One of the metrics that play a role to decide whether to have a provisioned disk or not, at least with AWS hosting, is the disk bandwidth.
For instance with a large enough disk, like 2000GB, I have max 250MB/s bandwidth with an unprovisioned (gp2) disk (the maximum), but could go to 500MB/s with a provisioned (io1) disk of that size.3 votes -
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 -
Allow log level to be configured per cluster/node
Atlas clusters don't support the setParameter command and, as a result, users aren't able to configure log levels. I understand the reasoning behind not exposing permissions to run setParameter to DB users so, in lieu of that, it would really helpful if Atlas users were able to configure log levels through the Atlas UI, preferably at the Node or Cluster level.
Thanks!
10 votes -
More detailed update status
It would be amazingly helpful to see more detailed information on recovering nodes. Just knowing that the node is, for example, "81% of the way on initial sync" is much more informational (and lets users know that it isn't stuck) as compared to the node being in "Startup2" recovery.
3 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 -
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
- Don't see your idea?