Atlas monitoring is great... but it would be super helpful to see a graph of banked iops. (or an approximation of this)

Suppose my iops limit is 100... and during the night my bank gets fully charged to 5.4MM.
During the heavy loads on my server, let's say my iops jump to a steady 500. This means that I am drawing 400 units from my bank. I can do this for 3.75 hours until my bank is exhausted.

It would be so helpful to see an iops bank balance drawing down during peak, recharging during off-peak... and thus getting insight as to when we need to scale up.

In Performance Advisor, I can see sample queries for each index suggestion.
They are formatted "nicely" for human viewing, but to actually investigate it, one would want to copy it as valid mongodb json, and run it with explain or analyze it in compass, or even just run it in a console to see how long it runs before and after the index addition.
However, there is no way of doing that, and I have multiple times "translated" the good looking ui to a mongo query so I could run it elsewhere.
This is a tedious and annoying thing (especially when you need to handle dates....).
Since you already have the data but chose to display/format it in a "nice" way, you also have the json behind it so please just let me copy it as json (with the proper ObjectId and ISODate or new Date() around ids and dates.

Thank you.

It is often practical to Live Migrate from one Atlas cluster to another Atlas cluster (e.g. to create another staging environment if backups are not enabled on the source, or migrate a production/staging environment to another dedicated project with minimal downtime).

Currently, the Live Migrate modal requires connection details from the source cluster, including the hostname of the primary, port, etc. Validation will fail if there are typos/errors in these inputs.

It would be easier to have a point-and-click option to "Migrate from another Atlas cluster" -- it could be a drop-down menu with names of other Atlas clusters in the project/organization that could be selected. The required connection parameters could then be automatically populated based on the particular cluster. A temporary user with the required permissions could even be created and then removed after the migration is complete.

This could make it easier to start Live Migrations between Atlas clusters, and avoid the need for the user to locate and confirm specific source connection requirements.

There might already be a way to do this, but I cannot find it. Please provide a way to combine "all primary" metrics into a single chart.

I love your metrics, but I hate that when primary moves from one server to another I get "data gaps" in my graphs. So then it becomes exceedingly difficult to look at temporal variations... requiring splicing together multiple segments from 2 or 3 different graphs.

I have attached a picture of what I am talking about. You can see that primary moved over for a few days so I get a graph with a hole in the middle. Please provide an option to "combine" all the various primaries into one chart.

Hi MongoDB team,

as the organization owner I don't want that my organizational members (developers, project owners etc.) have access to the billing section. Currently every member (independent on the granted rights) has the rights to see the complete billing section and can see the whole invoice incl. the names of the projects. This isn't acceptable regarding compliance because we are working together with external companies and their colleagues shouldn't have the ability to see all invoices.

Please make the billing section of MongoDB Atlas available to handle multitenancy - so that only the organization owner can see the billing section with all invoices. It would be perfect if you could also add the posibility for the project owner to see their invoices only (and not the ones from the whole organization).

I have also created a ticket for this problem: case 00716265.

Thank you so much!

Have a nice day
Christian