Feedback

Include “Tag” Field in the Cost Explorer API Response

We would like to request an enhancement to the API functionality to better support our reporting needs. Specifically, we are asking for a “tag” field to be included in the response from the following endpoint: https://cloud.mongodb.com/api/atlas/v...

Myungho Pok (복명호) about 1 year ago in Billing & Account Management 1 Submitted

5 VOTE

More information about snapshots and oplog sizes for backup optimization

Backup optimizations always involve costs. However, currently, we only have access to the number of GB we are consuming. I'm not able to tell which snapshots are full or incremental. Also, when Continuous Backup is enabled, I can't see how much I'...

Guest over 1 year ago in Billing & Account Management 1 Submitted

2 VOTE

break an invoice down to the database level

We have different application using different DB on the same cluster. current billing break down on the cluster level which we can't itemized the bill and know how much each application usage on the bill. would like to have bill break down usage o...

Guest 8 months ago in Billing & Account Management 0 Submitted

2 VOTE

break down usage on DB level on bill summary

We have multiple application using different DB on the same cluster, current bill has usage breakdown on the cluster level which we are not able to bill application for their usage, would like to have bill breakdown on DB level, so we can bill pro...

Guest 8 months ago in Billing & Account Management 0 Submitted

15 VOTE

Add information to the billing API reponse

When retrieving the billing details through the API, we are missing some information for a perfect understanding (and automation) : - Number of nodes of the cluster. Indeed, without this information, the field "quantity" is kind of complicated to...

Guest almost 5 years ago in Billing & Account Management 1 Submitted

4 VOTE

Surface hourly usage data and charges

Usage pattern can change very quickly throughout the day so a daily granularity of usage/cost is not sufficient for us to analyse usage behaviour. We need a further granularity which is the hour by hour usage and charges in order to help us moni...

Guest over 1 year ago in Billing & Account Management 0 Submitted

3 VOTE

Allow the ability when NVME cluster to autoscale up based on CPU and Memory

To provide autoscaling capability for MongoDB NVME clusters based on CPU utilization and memory metrics. This feature would automatically provision additional resources when predefined thresholds are reached, ensuring optimal performance during us...

Guest about 1 year ago in Performance & Optimization 0 Submitted

14 VOTE

Credits API

I need an API that will allow access to the items under credits in the billing page. This will allow me to pull this information daily into our master usage database to support our dashboards

Guest about 6 years ago in Billing & Account Management 0 Submitted

3 VOTE

Add support for all type of joins like Postgres has and improve performance

$lookup is a performance killer. Joins are crucial parts in every OLTP system. $lookup is the equivalent to join in SQL, however $lookup is slow, doesn't support hash joins or other efficient join algorithm implemented in Postgres for example. Se...

Guest over 1 year ago in Performance & Optimization 1 Submitted

13 VOTE

billing

The billing invoice is split by project. If we have multiple team in the same project, it a puzzle. We need to bill by cluster in this case.

Guest almost 6 years ago in Billing & Account Management 4 Submitted

Please enter your email address

FILTER BY CATEGORY