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.5 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)
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?3 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.1 vote
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.1 vote
- Don't see your idea?