Set up usage instrumentation to collect data to be used for Year One Report
We want bitpart to capture and log data to answer these questions:
- what user communities are using the service:
- so that we can describe with stories: types of workflows reflected against what is happening in the world
- what requirements are needed for maintenance moving forward
- what are groups or regions of interest (not usable until it is in the language native to their location; & what groups are using this will be dependent on how we roll out the languages);
- what is bitpart's volume of usage
- what are scaling up activities and future plans (product roadmap)
The following data should be able to be acquired from monitoring systems from bitpart and its dashboard:
**1. we can most likely gather from the monitoring platform:
- number of accounts created
- number of bots created
- number of bots created per type
- number of devices linked
- number of messages sent
- number of messages received
- approximate countries of origin of people creating accounts on the dashboard
- other dashboard usage statistics (i.e. login/logout times, number of sessions, possibly how long they spend on each page)**
- User info NOT currently covered in Bitpart's monitoring:
- what types of organizations are creating bitpart bots
- Domains, verticals
- Unknown data points:
- WHEN bots are being created, and make assumptions based on
Set up usage instrumentation to collect data to be used for Year One Report
We want bitpart to capture and log data to answer these questions:
The following data should be able to be acquired from monitoring systems from bitpart and its dashboard:
**1. we can most likely gather from the monitoring platform: