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.

We would like the possibility to freeze the row S S P (freeze the top row) when we scroll down to the different charts.

The metrics replset.replicationheadroom and replset.replicationlag would be useful to have exposed to identify network limtiations and/or too small oplogs

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 Team

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.

It would be awesome to have possibility to tag alerts in atlas when creating using API or console. It will allow to process groups by alerts by tags without keeping track of ids.
requires:
adding tag field to API create call
adding query by tag to API delete or update calls.

Pavel

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.

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.

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.

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.

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.

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.

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.

Like with other type of alert targets (Send to), we would like to be able to resend an alert to PagerDuty.

The reason is that an alert sent to PagerDuty can be mistakenly resolved but the real issue is still there, and the alert is still firing in Atlas.

Because it is already firing, it won't fire again so from that moment on, there is no way to get a notification of that alert so we might be missing a real issue.

If a user submits a configuration change to drop a shard, Atlas will sift through the cluster metrics and advise any necessary changes needed in order to complete the change without any errors/delays. For example, it will share the correct number of IOPS/cluster tier that needs to be used since the workload to drain a shard will increase; as well as other precautionary measures that should happen prior to dropping the shard (i.e. balancer needs to be turned on, etc).

It'd be REALLY useful if there was an ability to provide a label (basically a string) when creating a new connection to MongoDB from an application, to say where the connection is coming from.

For example we use a bunch of microservices and each API sets up a new connection. It'd be very useful to be able to see how many connections each API has at any given point, as it'd allow us to determine if the microservice is misbehaving with the database etc.

It would be really useful if the Atlas Metrics tab showed the node name and geographic location similar to how the Cluster Overview tab shows the node's region. In this use case, we have nodes located all over the world, so its useful to know where a node is located when reviewing it's metrics.

The uppercase "S" on the metrics which indicates seconds, can be slightly misleading as it can appear to be the number 5 when placed next to another number. This is especially misleading on the Replication Lag metric. It may be easer to read as a lowercase "s" or abbreviating with "sec".