[EPIC] Infrastructure Report for Pricing #34576
Description
Description
To support the repapering of customers in 2026 (moving them to usage based pricing) we need to be able to provide customers with reliable and accurate usage data so they can monitor their pricing tier and validate their invoices.
Usage based pricing is based on usage metrics from two areas:
- How much content you are managing in your dotCMS instance
- The amount you are using infrastructure resources in dotCMS Cloud
The ultimate goal is to provide customers with a dashboard they can log into and see all the pricing (and eventually other) related metrics in one place. But we need to support the repapering process happening through 2026, so we need something quick, even if temporary.
The high level strategy is to provide an in-app dashboard at each customer instance that will show them the content they are managing in the dotCMS production instance part of the pricing. Then provide the CS team with a report of the customer's infrastructure resources they are using that the CS team can download and send to the customer - thus giving them a complete picture of their utilization that goes into their cost. That will buy us time to develop the third piece, a self service dashboard that customers can log into themselves and access all the data that goes into pricing in one place.
This Epic is to capture the features for the second piece, the Infrastructure Pricing Report for CS managers to access and download information for specific customers.
Desired Outcome
Once this Epic is complete, we will have some sort of report or dashboard that is easily accessible by internal dotCMS personnel that can be easily queried to obtain the Infrastructure related metric for a specific customer.
The data for each customer that must be available in the report/dashboard is:
- Requests per month
- Bandwidth usage per month
- Storage usage
- Nodes being used by the customer
- CPUs being used by the customer
- Memory being used by the customer
- Environments (if they have a hosted Dev, Auth, Prod and how many)
The data must be easy to understand by the CS team and customers, and easily relatable back to the pricing sheet (things labeled the same). More specific requirements will be outlined in each of the subtasks.
A prototype that outlines the functionality needed and data needed is here:
Target Personas
- Developer teams
- Content teams
- DevOps teams
- System administrators (dotCMS)
Links
No response