Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
41 results found
-
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 monitor cost and spot pattern/irregularities.
3 votes -
Calculate Atlas Enterprise by sku
On the invoice, calculate the support value per SKU. Currently, the value of Atlas Enterprise is not included in the SKU.
1 vote -
Data transfer costs - Capacity Units Breakdown Invoice
On the invoices include the costs of data-transfer based on capacity units / hour. Capacity units are calculated based on 3 categories: "New connections or flows","Active connections or flows" or "Processed bytes".
One of the difficulties from the user perspective is to understand how much is the usage of our application on MongoDB is contributing for each category?Example: I was charged for 10000 Capacity Units for 3h, at $0.012 hour. Final charge is 360$. The problem with this is that I don't know what is contributing most for my cost, is it the "New connections"? "Active Connections? or "Processed…
1 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'm spending on oplogs and snapshots.
Without that information, I can't figure out if it would be better to reduce the Point-in-Time window, delete old snapshots, or change the snapshot policy.
I went through these documentation, but I still miss the actual sizes of snapshots and logs to make the correct decision.
- https://support.mongodb.com/article/000021504
- https://support.mongodb.com/article/0000210992 votes -
One tab or one button to quit from the whole platform without begging the support to help
There is no simple way to quit the service and erase the data. You have to go though clusters, projects and organizations without any links provided. The links given in messages are misleading. I had to work with helpdesk for almost an hour just to delete all my data that included: 1 organization, 1 project and two clusters.
1 vote -
Improve Atlas cost utilization tracking by time and label
Currently for any Atlas instance, cost granularity is limited to the cluster. It would be a significant improvement to enable cost utilization tracking by database for storage and compute. Specifically, storage and cost records should be granular in time and label, where labels can be assigned to databases. That is, as a common example with GCP for example, costs should be tracked by second, and in the billing data, aggregated to the hour by label.
This will allow chargeback, showback, and improved allocation methods for modern FinOps practices. As it is, MongoDB Atlas falls well short of any ability to…
1 vote -
Billing
What am I paying $60 a month for??? We only set it up and wired it to our Azure services; there is no data being run through it, we only hit it 2-3 times to test the APIs and make sure they work - it has been sitting dormant for 5 months, and I've gifted you guys over $300 as a result. HELP ME TO LOWER THE COST!!! Seems like a huge waste of money..
1 vote -
Expose billing usage on free tiers
An email was just sent out with the following information:
As a user of the App Services free tier, we have some exciting updates for you. After receiving your feedback, we will be moving to a daily free tier model that provides more clarity and makes it easier for you to track your usage.
In July, you’ll see an updated App Services UI dashboard that reflects this daily free tier usage rather than the current monthly model.
In this new model, the following daily free tier limits will apply:
• 50,000 Requests
• 0.5 GB of Data Transfer
• 25…1 vote -
Allow showing Total Usage chart based on Usage Date instead of Billed Date
On the billing page (cloud.mongodb.com/v2#/org/.../billing/invoice/...) there is a “Total Usage” chart that uses the Billed Date to paint the bars.
It would be great to be able to switch to the Usage Date instead.
This would help me to better understand on which day how much usage accrued in terms of costs. I am looking at it because I want to monitor the effects of changes that I made to the backup policy or the effects of code updates to reduce data transfer volumes.
Thanks a lot for considering this!
1 vote -
Allow Organizations without a Subscription to have linked organizations
Currently, to be able to link organizations to a single paying organization (ie. linked organizations), it requires an active (paid) subscription.
My use-case is that we have an enterprise subscription on our production organization, but wish to have a sandbox organization to test infrastructure as code, creating/deleting sub-organizations, and linking API keys.
In my opinion, developers / administrators should be able to test out managing the org structure in a separate account without affecting the primary "root" paying account structure.1 vote -
View billing information at project level
I think it would be a good idea to be able to see billing/invoices at project level. So the project owner will only see the consumption of his projects.
By giving project owners the "Organization Billing Viewer" role, we make it possible for them to see the billing for the whole organization. A new role for the project owner to view only their own project invoices would be nice.
6 votes -
Request for Enabling Vendor-Metered Tagging on AWS Marketplace
Hi Team,
We are currently utilizing MongoDB services via the AWS Marketplace and have encountered an issue related to cost allocation tags.
We have recently been working on improving our cost management and reporting processes within AWS.
A key component of this effort involves leveraging AWS-generated cost allocation tags, particularly those prefixed with "aws:marketplace:isv:".
However, upon review, we have noticed that these specific tags are not available or being applied to MongoDB services that we are using.The absence of vendor-metered tags for MongoDB on AWS Marketplace is hindering our ability to effectively track and allocate costs associated with your…
16 votes -
Support resource tags included in billing ingestion dashboard while filtering Charts billing dashboard by resource tags
It's important to support resource tags included in billing ingestion dashboard and filtering the charts based on these resource tags. Include the resource tags in Atlas billing dashboard as filter/group criteria
1 vote -
1 vote
-
Include the MongoDB VAT number in the automatically generated invoice
As a foreign company, it is necessary to have the VAT number of the invoice to proceed with corporate expense deductions.
1 vote -
Provide a more granular breakdown of monthly Atlas billing (in the Azure dashboard)
Provided more flexibility/transparency into the monthly Atlas spend for Azure marketplace customers (in the Azure billing dashboard). Ie. allow users to break down spend by project, tag, cluster etc.
Currently, only a single total monthly spend value is available in the Azure dashboard, with no additional details.
1 vote -
Restrict Organization Subscription/Credit to certain Project(s)
We want multiple internal groups to belong to a single Payer Atlas Organization for our company to simplify management but those groups also have separate internal cost centers.
Currently if any single project purchases atlas marketplace subscriptions or commitment subscriptions, they can be consumed by all projects in the Organization (and linked organizations). We want to ensure that only the projects for that purchased the subscription can utilize the subscriptions they paid for.
This is similar to AWS Compute savings plans, where by default they are spread/utilized by any member organization account but you have the flexibility to restrict only…
1 vote -
Data Usage Reporting & Improved Profiler
The Current Problem:
The existing issue stems from MongoDB's inability to provide concrete evidence supporting the data charges for your data usage. This predicament becomes especially troublesome when your system typically operates within a data usage threshold of less than 100GB daily. Suddenly, over a span of 7 days, you are billed for data usage exceeding 1000-2000GB daily, only to subsequently revert to using less than 100GB daily. The absence of substantiated evidence leaves you in a quandary, unsure whether the issue lies with your system or is a reporting error on MongoDB's part. MongoDB Support relies on the slowest…1 vote -
Add more detailed information about SUSPENDED account state
When an account get susspended due to some debt on invoices. Please add a detailed step by step process indicating how the service gonna be stopped after some time. This, becuase today in the email, you only say "please pay the invoice" but you don't give clear information of how or when the cluster gonna be innaccesible to be used (this process is not clear for customer service neather). Note, some time change the payment method can take some time and depend on other instituition.
1 vote -
Request billing invoices via API calls at project and cluster level
We need the possibility to request billing invoices via API calls at the project and also cluster level.
The information should be available as it is broken down in the invoices that can be downloaded from Atlas as a csv file.1 vote
- Don't see your idea?