Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
175 results found
-
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 -
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.
12 votes -
Monitoring Integration with Splunk
Unlike a connector (https://feedback.mongodb.com/forums/924145-atlas/suggestions/40688308-splunk-connector-for-atlas) it would be useful if Alerts could be sent to Splunk.
16 votes -
New view with connection statistics
It would be valuable to have a per-cluster view showing an overview of connections into each cluster including:
- The number of connections per hours (opened, closed == churn)
- Which IPs connections are coming from and how many from each over time
- What drivers are being used for these connections and from which IPs
- Which user is opening the connections
This information can be very useful in understanding which applications/microservices are opening up the most connections, and helping to find old drivers etc.
28 votes -
Disk Usage Breakdown
When looking at the cluster page, I can see Disk Usage = 1.6GB, for example, but I don't know what the breakdown of that is. For instance, if I look at the same DB and add up the size of the collections themselves it's barely 1.5MB. So 1.6 Gig disk = 1.5 Meg data. I suspect this is oplog etc. but it is a pretty confusing potential red herring when diagnosing performance issues etc.
2 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 -
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 -
eviction metrics
Please include eviction metrics as well in monitored metrics in atlas so that it will provide an overview how many evictions are happening in particular time and there by decide correct memory for the instance.
1 vote -
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 -
Atlas Cluster Labels in UI
With the Atlas API, there is functionality to add labels to various clusters like EC2. It would be great if that was exposed through the Atlas UI as well.
19 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 -
Alert for WiredTiger Cache
Hi,
Can you please create an alert for WiredTiger metrics, such as used cache?
We had several cluster instances going over the 5% of used cached (dirty data) and would like to be notified when it happens.
Regards,
SergeiThis is needed in order to determine whether
7 votes -
Allow to create Dashboard
Please provide feature to create a dashboard for metrics like CPU, memory consumption etc for a cluster or more than one cluster in single graphs like for cpu one graph, for memory one graph like that just like monitoring tools provide for example zabbix screens and dashboards, stackdriver dashboards, dynatrace dashboards.
This is to have a glance on our entire architecture instead of checking each and every cluster every time. This will be particularly useful during load tests or business peak period where we need to check more than one cluster performance.
4 votes -
Separate metric graphs of egress outside the region per database, collection, user, destination
Separate metric graphs of egress outside the region per database, collection, user, destination, so that I can easily find out what is causing the egress traffic which is billed on my account. This will also help me identify what parts could be good to move to different cluster in another region closer to the user,
1 vote -
Allow default settings on alerts on project/organization level
It would be great if there was a way to set the default notification channels for alerts on the project and organization level.
I was recently informed by the support team that there is no possible way of doing so, and that all alerts should be changed individually rather than for the whole project in one go.
1 vote -
Show in the UI when an index build is ongoing, and when it completes
When indexes are built from an application or a mongorestore there's no way to see if it's ongoing in the UI.
There should be an indication in the "Real-time" tab saying that an index on collection X is in progress. This would explain why performance is currently impacted.
It would be good to see index start and end marked on the "Metrics" visualizations so we can see the impact of index builds on IOPS, CPU, memory etc. This could help understand if we need to upscale the cluster.
9 votes -
Stackdriver Integration
Atlas Monitoring UI is great, but to ease centralization of alerts and dashboards..., it would be nice to have all atlas metrics in Cloud Monitoring too.
9 votes -
Elections bar colors in Metrics should be more vivid
The atlas metrics show node election statuses in colors - red/orange and brown. When there are multiple re-elections in a short period of time, these all merge together making it hard to decipher the order of occurrence - especially the near overlap of orange and brown Having vivid/contrasting colors should make debugging easier.
It would be helpful if some aspect about the x-axis would tell you what status the node was in at a given time. For example: the x-axis is also that color from time X to time Y, and then the node was demoted/down and the axis turns…
23 votes -
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.
6 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
- Don't see your idea?