Metrics reports
- Dominant language
- Python
- Stars
- 18
- Forks
- 11
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 20
Description
## Admin
- MRR
- Churn
- Failed Payments
- Gateway success ratio
- Profitability
- Unit Profit (what we are getting or losing per VM)
- Invoice sync/creation failure
- Uncharged payments
- Limits violations
- Stuck Invoices
- Service/Product wise revenue
- Atlas consumption
## Customer
- Forecast
- Tag-based consumption
- Payment History
- Failures with reason
- Credit Ledger
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by turning the Admin and Customer lists into agreed report requirements, including definitions, data sources, and expected views for each metric. Identify the reporting entry points and validate how MRR, churn, payments, invoices, consumption, and credit history should be calculated. Done means the requested reports are implemented with verified results for both audiences.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- analytics, payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100