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
-
Send Alert when IP access list changes
Customer is requesting that an alert be sent out if project IP access list gets changed
21 votes -
Include Username in Profile page
The profile page would be more use if the listing included the username so you could work out which application was making the queries.
1 vote -
Keep context of Metrics dashboard
on MongoAtlas metrics dashboard, I can organize graphically different metrics as I want to display first "insert" metric for example, then "cpu" metric, etc ...
If I change this actual order, then I go to another screen (for example "network access") and finally I come back to this metric dashboard, my new metrics added (insert, cpu, ...) in first position are not in wanted first position (at the top of metrics list), but at the end of this metrics list.It would be great to keep metrics context (displayed metrics and ordering) on Metrics dashboard.
8 votes -
Provide offending query shape in Query Targeting alert notifications
It would be ideal if the alert notifications for Query Targeting ratio alerts included a reference to the query shape that caused the alert to fire. This would assist customers in locating the exact query/queries with poor targeting ratios so that they can be optimized in a more expeditious manner.
8 votes -
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 -
Metrics
We would like the possibility to freeze the row S S P (freeze the top row) when we scroll down to the different charts.
2 votes -
Add support for replication lag and replication headroom metrics in Datadog
The metrics replset.replicationheadroom and replset.replicationlag would be useful to have exposed to identify network limtiations and/or too small oplogs
2 votes -
Disk queue length metric
Atlas exposes a few hardware metrics including Util% (presumably obtained from iostat or similar). However this metric is not very significant in the age of SSDs - a volume could be 100% utilized and still have spare capacity. A more useful storage-level metric is Average queue length - this is easier to interpret (high queue length = storage contention).
Would it be possible to add this metric to Atlas monitoring?
11 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 -
Allow to set billing alerts per project
I have different projects where I expect and calculate with different costs. I would like to set billing alerts per project, for example if an internal evaluation projects execeeds a specific biling the threshold is probably lower then for a production project.
Similar to the currenty billing alerts, I would to set a billing alert, but either per project or with different thresholds for each project.
2 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 -
Google chat integration with Alerts
Integration Alerts with google chat like done with SLack
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 -
Increase monitoring metrics resolution retention time on views of 1min & 5mins
The speed at which usable monitoring metrics data (1m, 5m) is purged and reduced to 1hr is way too quick.
After 1hr, the ability to analyze these metrics that are crucial to investigating a performance issue were lost and hindered the root cause analysis.
I would suggest that 1m or at least 5m resolution metrics be retained for at least a week before being purged.
20 votes -
Webhook
Hi MongoDB Atlas Team,
Some of enterprise customers are left out with improper monitoring via Webhook to ServiceNow (an ITSM tool). Can you please improve on it so right set of fields can be included like "Priority", "Service", "Assignment Group" etc. other details which can be filled up via dropdown or entered manually so alerts to generate incidents via ServiceNow.
Regards,
Varun
Toyota Europe Database Team8 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 -
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 -
Show max IOPS line on IOPS graphs
When monitoring disk IOPS, it isn't immediately clear when we are limited on IOPS. Having a red limit line on the IOPS chart on the metrics tab would help here.
17 votes -
Automatic information when shared cluster is throttled
When a shared cluster has reached it's limit and the cluster is throttled, an email should be sent to each db-owner affected. This would save your customers AND your support a lot of time troubleshooting.
Right now there is no way for a db-owner to see this information, let alone get that information, except for asking support for help.
15 votes
- Don't see your idea?