Similar to how AWS includes tags/labels in their billing dashboard, I'd like the ability for my cluster labels to be included as a column in my billing usage details (or even the exported CSV).
This will allow me to categorize my billing usage as granular as clusters in addition to the current method which is by project.18 votes
I support multiple orgs and projects falling under my enterprise. I'd like the ability to tag projects using a key value pair - similar to GCP, Azure, AWS. Tags will help us organise and understand what's running in our projects.
Basic functionality that operates on tags will be helpful like filtering projects and enhanced billing that can group costs based on a tag would be beneficial.
Right now, we need to add cost metadata to the project name, which is the only place where we can do so.14 votes
on behalf of the customer,
would be great if we could allow tags on Org/ project level for cost allocation reasons (similar to how AWS allows this). When creating a project we can eg. add the type of environment, cost centre, bearer etc - without it showing up in the name. Does not necessarily need to show up on the invoice but we must be able to create a view which includes this info.8 votes
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 interpret
- Group Name. Each entry is attached to a groupId, but sometimes when the project has been deleted, it is impossible to retrieve its name, so pretty complicated to interpret (in the UI, the group name is available, so I guess it can be in the API)
I work for a company that has multiple departments and we need a way for monthly usage reports to be sent out to each project owner.5 votes
Even if a project has been closed, it would be good to see what the name was. After all, the project ID shows up in the bill, why not the project name?4 votes
I support multiple business units (BU) within our company. Each BU uses multiple applications & teams. In order to offer service in Atlas, through automation, there is no option in Atlas to create/ delete Organization dynamically. It allows managing Projects and below.
It will be good to add this feature to create/ delete Organization dynamically.
It will also be good to manage, ie to create different Accounts dynamically (like AWS/GCP).
This will help to have separate account & organization, for each BU to manage billing and manage the consumption, through automation.
Rama Arumugam3 votes
Accept cryptocurrency payments for billing purposes as Paypal or Cards are very unreliable. Recommended cryptos - Bitcoin (BTC), Ethereum (ETH), Bitcoin Cash (BCH), Dash.
Commerce between users and mongoDB platform will greatly improve by allowing payment mechanisms that have instant transactions at a much lower fees.2 votes
For CrossOrg Billing - should allow this role to see billing details of linked orgs (IN linked Orgs)1 vote
Some countries use debit cards primarily so it would be great if we could have that option as a payment method.1 vote
Add PIX payment method. I don't know how much of a hassle it's to implement such payment method for brazillians, but I think it would be one of the "killer feature" for us. Thank you.1 vote
- Don't see your idea?