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.

We find the conditions for billing alerts to be very limited. We were hoping we would be able to setup an alert that triggers when a certain threshold of our total subscription amount has been used for better monitoring. For example, >= 75% of the total subscription amount is used.

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.

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.

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.

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 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.

Hi Team,
We understand that network whitelist information (IPs added/removed) will be available only in portal under project activity feed. As our requirement is to access this information via API.

Please let us know is there any feasibility of having these project level network whitelist information through API or in db logs in near future.

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).

Timestamps in Metrics plots are displayed in 24-hour time format, but the date/time filter inputs require 12-hour time (using am/pm).

screenshot: https://p-37FYgJ.b1.n0.cdn.getcloudapp.com/items/L1upe7Wv/Image%202020-06-25%20at%204.28.22%20PM.png?v=ec3b0551ea4035a207a90ab83817bba6

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?

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.

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.

Please provide feature to create a dashboard for metrics like CPU, memory consumption etc for a cluster or more than one cluster in single graphs like for cpu one graph, for memory one graph like that just like monitoring tools provide for example zabbix screens and dashboards, stackdriver dashboards, dynatrace dashboards.

This is to have a glance on our entire architecture instead of checking each and every cluster every time. This will be particularly useful during load tests or business peak period where we need to check more than one cluster performance.