We can specify date format but the time format is limited to 12hr clock. Please allow us to specify 24hr so the activity log and rest of the UI is a little easier to read. Thanks

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?

Provide some callback method (webhook URL, push notification, etc) that an API call can use to indicate it's done. That way the user doesn't have to sit and poll endlessly.

Some examples of where this would help:

• After creating a restore job, waiting for the snapshot download URL to be ready.


• After modifying the automationConfig, waiting for all agents to report that they're in goal state.

To be able to change and read Organizational Settings in an automated matter, support for Organizational Settings should be added to the Mongo Atlas API.

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.

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.

Allow creation of collections and indexes via terraform atlas plugin. The use case is that, when an atlas cluster is being set up, we want to enable the indexes on the collections from the start.

Managing permissions for users is a pain right now. It's a lot of clicks, it quickly becomes messy and sometimes the modal closes without saving changes.

It would be a lot easier if we could import a CSV containing all permissions for a certain user (user name, permission type, database name, collection name)

Hi Team,

We need to give access to a particular team so they can create, edit, clone, disable, and delete the alarm for the entire organization in Alert setting only.

We should not give them access other than the Alert setting. Is there any way to give access for Alert setting only, kindly provide your suggestions at the earliest.

Please provide us steps if there's any way to create custom access for alert settings alone.

Currently the Query Profiler can plot queries that were logged up to 24 hours in the past.

It would be helpful to allow for visualization of a custom date range older than 24 hours ago, rather than only queries logged within the past 24 hours. This could help with RCAs for events that occurred more than 1 day ago, and also help teams who collaborate to investigate queries over a time period longer than 1 day.

Similarly to how database user data access permissions can be configured on a per-database or per-collection basis, it would be ideal if Atlas user data access permissions (as they apply to Data Explorer) could be configured on a more granular basis as well.

add more to the status of the online archive - for example, if I set it to 7days back it's good to know that currently at 80days.

An example: for a very big collection it takes long time to archive - so either show a % left until it caught up or show number of days currently at

other nice details: number of documents archived, archive rate, etc

I would like to see documents inserted into the database in a shell show up on the cloud data explorer UI in real time without refreshing the screen.

It would be great to have a function where we can , using only atlas interface to filter a month and a year , and we cann see historical data about sizes.

Autoscaling clusters down a tier doesn't seem to work very well. Even under rather low memory usage, it doesn't seem like the procedure really ever triggers.

Right now I have to give an admin permission to allow someone on my team to query snapshots from a backup (i.e. downloading the tunnel file).
I don't want to give an admin permission just to allow our data analysts or a developer trying to understand data corruptions to view the database at an older date.

As an ex-mLab customer, I used to really enjoy having common queries on collections saved, like "find a customer", "list latest X" etc Is a dropdown with a name and the query, so when you select it you can quickly perform the search.