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
-
Publish statistics in Atlas to analyze what is filling oplog
It would be very useful to be able to see metrics/statistics about the contents of oplog. There are open-source tools like oplog analyzer (https://github.com/mhelmstetter/oplog-analyzer) that can be used, but it's a hassle to have to install it and run it in the same datacenter where the database is running (for performance).
The statistics I'm most interested is what collections have most oplog documents, what kind of operations they have been and what is the total size that each collection currently utilizes from the oplog. This will help improving code to use less oplog.
We've seen cases where bad…
3 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 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 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 -
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 -
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 -
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 -
Show Cursor Not Found Errors (telemetry)
We have a lot of cursor not found errors and currently there isn't an easy way to locate them at the Atlas integrated monitoring.
It would be nice to have this feature.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 -
Show shard node name in alerts
When receiving tens of emails regarding a dangerous condition on a node it would be helpful to know which node instead of having to click in the email to get to the portal to know if the issue affects our primary node or a secondary node.
Thanks
1 vote -
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 -
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 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 -
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 -
Stream profiler data to external services
Currently there doesn't seem to be a way to set up custom alerts and monitoring on specific metrics such as when the size of documents returned form a query exceeds a certain limit, even though that information is available through the Profiler when looking at query samples.
It would be very useful to be able to either configure these metrics to be sent to an external service like Loggly for better monitoring and alerts or allowing to create customized alerts/webhooks within Atlas that would be triggered based on a custom-specified condition.
1 vote -
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 -
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 -
Profiler window should auto zoom to sampling period and show sampling period range
Atlas documentation states that the Query Profiler shows up to 10,000 queries within the past 24 hours: https://docs.atlas.mongodb.com/tutorial/profile-database/index.html#data-display-limitations
However, it is confusing to see that the Profiler cannot show more than a couple hours of data, likely because it is hitting the 10,000 entry limit.
The plot still shows a view showing 24 hours of time, but only the past couple hours have data plotted, misleadingly indicating that there are no slow queries before a couple hours ago – here's an example: https://p-37FYgJ.b1.n0.cdn.getcloudapp.com/items/JruWZDYK/Image%202020-03-25%20at%2010.49.32%20AM.png?v=7f79362e62c8d15a9f91f8ba4d5aecaf
Atlas should make the sampling time window clear in the Query Profiler graph so that we…
9 votes
- Don't see your idea?