Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
-
Graph connections per user (or per database)
Show a graph of connections per user.
It would be very useful to see how many connections each user has (or also, each db) over time.
It would allow us to see more clearly and faster which service uses how many connections.
7 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…
20 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.
12 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 -
Add Alerts for Triggers
Add alerts for when Triggers are suspended or exceed a threshold.
11 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 -
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 -
Improvement: Add severity to alert definitions in Atlas MongoDB
The alert payload only contains status field with 'open' or 'closed' value. No severity definition option is available.
12 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.
7 votes -
Email subject more specific for Alerts
The email Alerts that MongoDB provide are very useful, especially the Oplog and CPU Usage. However, the subject of the emails are not clear and does not specify the Alert type. It is just a generic "Alert". It would be great if MongoDB can add "Alert Oplog" or "Alert CPU Usage" to the email subjects to make them much more clear and helpful. Thanks!
13 votes -
Yellow exclamation icon should have a tooltip or explanation
Often in the cluster card, or in the cluster panel, one or more processes are marked with a yellow warning icon (instead of a green dot). However there is no indication about what this means or how to fix it.
Can there be a tooltip or explanation about what this icon represents?
27 votes -
Alert setup for failed logins
There is no good monitoring or alert functionality for dealing with potential invalid login attempts.
I suggest an alert setup to handle events when known users fail more than 3 times to login (either in Atlas or via driverlogin to db).
We have had an external audit done and this is something they have found as a shortage in the MongoDB Atlas environment.
Log files are good but not to monitor potential security issues
5 votes -
Show driver/application/user metadata in Query Profiler query summaries
It would be helpful if the Query Profiler showed the driver and user metadata associated with the connection over which a particular query was run.
After clicking on a particular plotted operation in the Query Profiler, the sidebar pops up and shows execution statistics and structure of the plotted op, but doesn't show anything about the driver/application/user that issued the command.
This query summary would be more actionable if the driver, driver version, application name, and user were also displayed in the query sidebar (these details may be recorded in a separate log entry from the command itself).
This information…
8 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 -
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.
9 votes -
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 -
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.2 votes -
host down alert automatically silenced during atlas maintenances
Our clusters keeps sending loads of alerts during maintenance times about host is down and similar - it's logical and I understand that those are rolling updates so the functionality of the cluster is not affected. However it's quite unfortunate that host are down for quite a while (20 - 30 mins sometimes) and as we don't want to create unnecessary noise from atlas monitoring we had to bump up our slack and pager duty notification to be fired 30+ minutes. This covers maintenance but out of maintenance this is ridiculously high and we would like to know there is…
8 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.
7 votes
- Don't see your idea?