Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
160 results found
-
Add replica set name to cluster info main page
It would be nice to get quick access to the name of the replica set from the cluster overview page.
7 votes -
Trigger execution details
It would be very useful to have some details provided in Atlas to trace the execution of the trigger, like the _id and operation type at a minimum. When a trigger executes the only information we see in Atlas is [
"Sent to AWS EventBridge"
].6 votes -
Atlas activity feed
We want option to export Atlas activity feed in a file to export and work with it. Parse it etc ...
Even better, make a collection with it.
6 votes -
Allow Atlas to send additional metrics to New Relic via integration
This is a request to add some additional metrics to those that are currently sent from Atlas to New Relic when the integration is enabled.
The specific metrics of interest here are:
- Disk Space (%) Used (or Free)
- DB Storage
- Query TargetingHaving pointed out the above metrics specifically, I would also say: the closer that the metrics sent to New Relic via the Atlas integration can resemble those available in the Atlas cluster Metrics page, the better.
6 votes -
Change Streams Monitoring and Alerting
Change streams can cause performance issues if not used properly. In some cases, administrators of multi-tenant dbs have no control (and shouldn't) over how various clients create change streams.
I think it is important that we accommodate these use-cases and provide useful metrics in the OM/Atlas metrics pages, and alerts on those metrics. Some potential metrics:
1. Number of change streams open
2. Average change stream lifetime
3. Query targeting ratios for change streams
4. Avg time between consecutive polls of the change stream (and other statistics)
--thought here is that change streams that are polled infrequently will result in…5 votes -
Monitoring for WiredTiger data handles
Add process measurements for monitoring WiredTiger data handles.
From Atlas documentation https://docs.atlas.mongodb.com/reference/atlas-limits/#collection-and-index-limits :
While there is no hard limit on the number of collections in a single cluster, the performance of a cluster might degrade if it serves a large number of collections and indexes. Larger collections have a greater impact on performance.
but now there is no way to get this information except
db.serverStatus()5 votes -
track collection size
I would like to be able to track the size of our collections (i.e. # of records, total disk size) over time. It would be ideal if there was an automated way to do this with Atlas, perhaps with Charts ?
5 votes -
Add horizontal scroll bar to metrics tab
I can't see metrics for all of my nodes while in the metrics tabs unless I make the window very large. It would be much easier to analyze the health of my cluster if I could review metrics for all the nodes by scrolling horizontally, rather than having to switch between a grouping of nodes.
5 votes -
Use 24-hour time format in Metrics date pickers
Timestamps in Metrics plots are displayed in 24-hour time format, but the date/time filter inputs require 12-hour time (using am/pm).
12-hour time is not widely used around the world, and it is cumbersome to use in the date pickers especially give that other parts of the UI use 24-hour time.
Can we update these date pickers to use 24-hour time instead?
5 votes -
Allow NewRelic integration to use EU APIs instead of default US APIs for clusters in EU region
The NewRelic integration in MongoDB is using the default NewRelic API that is in non-EU region. There is a separate API endpoint for EU region, that is described at https://docs.newrelic.com/docs/using-new-relic/welcome-new-relic/get-started/introduction-eu-region-data-center#.
This is causing 'newRelicLicenseKey' failed to authenticate error for the MongoDB Atlas cluster setup in EU region.
5 votes -
Expose Locking Metrics
One of our customers have asked if we can expose locking metrics through the Atlas UI to assist with investigating suspected lock contention issues.
We have this information in FTDC and our customer feels it would be helpful for them to have this information too.
4 votes -
CPU Steal % on Azure
The CPU Steal % metric and alert seems to be currently implemented only for AWS. Please implement it also on Azure, as there is no easy way currently to get alerted if the underlying burstable VM (e.g. for M20) runs out of credits ...
4 votes -
Show date in UI DB Stats axes
Show date in UI DB Stats axes
Currently the x-axis of DB Stats charts do not show dates, making it difficult to interpret the range of time displayed in the chart.
For example, you can see in the date menu shown in the attached image that the chart range is over 4 days, but this is not apparent in the x-axis of each chart -- the x-axis only shows one reference time of 07:00.
It would be more helpful if the axis showed a reference date in addition to the time, and ideally a couple dates so that it is…
4 votes -
Log Redaction for Atlas
It would be good to see Log Redaction work in Atlas as well, similar to On Prem
https://docs.mongodb.com/manual/administration/monitoring/#log-redaction4 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.
4 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.4 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 -
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 -
Extend sub-hourly metrics retention to 72 hours
Right now the 1- and 5-minute metric data is lost after 48 hours (when it is combined into the hourly data). This makes it impossible to take a close look, on a weekday, at an event that occurred over the weekend.
It would be nice to be able to look at a problem on the weekend and say "I'll look at this more closely on Monday", and then have the ability to actually investigate it on Monday.
4 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
- Don't see your idea?