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.

It is very difficult to discover the TTL of a given collection. It would be great if the TTLs for each collection was visible in the collection UI.

Right now collections are only shown first added first. I think it would be useful to be able to look at the last added first.

Currently, it is not possible securely create a user in a terraform DevOps pipeline, since "Passwords may show up in Terraform related logs" according to the documentation. If the password was no longer required to create a user, we could avoid this issue by only using certificate authentication.

We would like to see better compression for data stored in the Online Archive.
Data in our cluster is compressed very well using the WiredTiger storage engine.
Moving it out into the archive grows our data size by almost 4x.

Hello,

after a discussion with a MongoDB architect during a consulting day, the rename of a database was possible in previous version of MongoDB but now, it's impossible without a dump / restore process.

We don't want use a dump/restore process to rename a database because it's use a lot of time.

Could you tell me why this feature was deleted ? and will it be possible in a future MongoDb version ?

thanks.
regards,
David.

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.

During an index build from atlas the only status update you see is:
"We are deploying your changes (current action: configuring MongoDB)"

When checking the logs of the replicaset memeber you can actually see the percentage of completion on that member of the replicaset:

2020-11-25T11:15:44.002+0000 I - [conn12] Index Build: 54798100/206784433 26%

It would be nice to have this percentage displayed through the UI.

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.

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.

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.

In the comparison between clusters, for Shared clusters M2, M5, vital information is that there are data limits and those limits are shared, not only for you but also together with any other databases of the same cluster.

This was NOT clear at all when we signed up with an M2.

Hey there,

I know it's hard for big companies to get along, but I'd love to have a seamless experience for using MongoDB alongside DO's new PaaS offering. Can you all strike a deal please?

Our Mongo cluster has had to resync. It would be great to get some kind of time estimate or progress bar to know how far it's got in resyncing so we can let our research team know when the cluster will be ready again.

Make EBS Burst Balance Metrics available within the Atlas UI. Currently it is not easy to 100% understand how much burst credits are being used and whether they have actually been depleted.

You can infer it from the IOPS metrics going above baseline IOPS and then suddenly dropping down but would be better to see the balance itself to be 100% sure. This will save support requests to do so.

Please include the human-friendly cluster/host names in Monitoring Alert Notifications (e.g. email, PagerDuty, etc) in addition to, or instead of, the less clear internal cluster/hostnames (i.e. atlas-abcdef-shard-0).

To speed up recovery after restoring from a snapshot or having a node replaced, it would be nice to have the option to use AWS Fast Snapshot Restore

https://aws.amazon.com/blogs/aws/new-amazon-ebs-fast-snapshot-restore-fsr/

This would allow the disk to have full performance as soon as available.

Filing this on behalf of customers that are having a hard time telling orange and brown apart in Atlas metric timeline annotations (node become secondary, node becomes primary)

Within Atlas today, we have a number of channel options to send alerts (Ex. OpsGenie, Slack, VictorOps).

I would like to see a hook integration provided by Atlas so any tool can recieve alerts from their cluster. Ex. I can recieve my cluster alert in Microsoft Teams.

3rd party hooks can increase the stickiness of Atlas and improve freedoms for teams and their existing toolsets.