As a sales person I want an application that can parse subscription transactions into a reportable format and a way to query the data, so that the company can get a more accurate assessment of the state of their subscribers and their business transactions.
Description
Due to time-to-live limitations of Humio, a different option is needed to report on business intelligence. The audit type logs will be obtained from an endpoint at Mono Solutions and will need to be cached in a history server. It is needed for mono solutions sales department to be able to view subscription transaction, business intelligence and be able to report on it in a queryable way.
The solution needs to be able to report on:
Percentage of subscriptions changed along with a breakdown per percentage of the final subscription
Percentage usage of individual site user groups
Ongoing Churn rate (new subscriptions vs terminated subscriptions) for both paid and unpaid subscriptions.
List of requirements
Infrastructure
[ ] Setup a middle-ware solution, that needs to be able to connect to obtain logs from endpoint at mono solutions and send logs to storage #6
[ ] Setup a history server for caching unstructured data.
[ ] Setup a key-value store for semi structured query able data. #7
[ ] Find a suitable dashboard application #2
[ ] Create dashboard application for reporting on business intelligence #9
Dashboard Reporting - Use cases
[ ] View percentage of subscriptions changed along with a breakdown per percentage of the final subscription #17 #19
[ ] View percentage usage of individual site user groups
[ ] View Ongoing Churn rate (new subscriptions vs terminated subscriptions) for both paid and unpaid subscriptions. #18
Acceptance Criteria
[ ] The system should be able to be deployed on amazon AWS Cloud Services, so do a containerized solution.
[ ] System logs should be reformatted and sourced to a main.log file, so the logs can be shipped humio. #13
[ ] The Application state should be resillient to failure and not rely on Mono Solutions existing databases or API. So store events in a history(cache) server. #11
[ ] It should be possible for Mono Solution developers to maintain and extend the system. So documentation is needed. #AddReference
Non-functional requirements
[ ] Needs to be responsive
[ ] To ensure the code is performant
[ ] Ensure the code doesn't require excessive load from Mono Solutions existing API or databases
📋 Business Intelligence Reporting
As a sales person I want an application that can parse subscription transactions into a reportable format and a way to query the data, so that the company can get a more accurate assessment of the state of their subscribers and their business transactions.
Description
Due to time-to-live limitations of Humio, a different option is needed to report on business intelligence. The audit type logs will be obtained from an endpoint at Mono Solutions and will need to be cached in a history server. It is needed for mono solutions sales department to be able to view subscription transaction, business intelligence and be able to report on it in a queryable way.
The solution needs to be able to report on:
List of requirements
Infrastructure
Dashboard Reporting - Use cases
Acceptance Criteria
Non-functional requirements