Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
176 results found
-
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 -
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 -
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 iops
The Disk IOPS graph shows 2 colored lines. (read/write). It would be great to add a third line which is the SUM of the 2 lines. Or... a toggle switch so we can see the sum line instead of the 2 components. Thanks!
15 votes -
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 -
Option to group Profiler records by query pattern
The Profiler shows slow query statistics grouped by namespace, but it would also be helpful to view query records grouped by query pattern (perhaps similar to the "pattern" group option in mplotqueries: http://blog.rueckstiess.com/mtools/mplotqueries.html#group-by) and/or by specific fields used in the query.
This could be helpful, for example, for identifying particular query shapes that are executing slowly or suboptimally so that these can be investigated in more detail.
2 votes -
Lower Roles Should be able to access RealTime Performance Panel
As an Ops person, access to the Realtime Dashboard Role is important, but it seems like in order to see it, you actually need access to the data itself. Is there a role that can give us that realtime monitoring without requiring access to the data explorer? I can access Profiler and Performance Advisor without those restrictions so it isn't clear as to why I can't also access the RealTime Performance Panel. Both of those show as much or possibly more information with regards to collections, documents, indices, etc than what appears on the RealTime Performance Panel.
1 vote -
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
- Don't see your idea?