-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Establish network usage metrics #13
Comments
@freimair Could you please provide the tasks that are needed to complete this project? |
I'll just add here that the purpose of this project as originally conceived is to support our goal of improving onboarding. We need these (certain, specific) metrics in place, with some historical baseline being established, in order to effectively measure whether our new onboarding workflow implementation is actually helping anything. @ripcurlx, I'd suggest transcribing that and whatever else you see fit to the |
Transcribed the relevant parts from the issue into the |
here is the tasks list
|
Thanks! Regarding the two unplanned task: Does this change the estimated budget above? If yes, by how much? |
yes, these tasks require an additional 550 USD for me (and 200 for wiz i believe) already acked by @wiz as part of the opsdev budget. |
So the total amount for this project is 2750 USD, correct? |
which amount belongs to which budget is for you guys to decide. |
here is a preliminary set of graphs. Please note that the network size is only provided by one pricenode and is multiplied x8 for a rough estimation of real numbers. We have to discuss the second KPI, ie. |
Report Review Meeting 2020-03-19
|
It's great to walk through the dashboard and see this data! |
@ripcurlx, can you provide an update on this project? |
All the distributed deployments have some spurious issues every now and then. Need to get myself access to a live pricenode to figure out what is going on. And I need some more budget. Depending on the issue, +550$ should do. |
found the error, at least it seems like it. There are no more gaps in the last 30+ days (except for the time where pricenode have been upgraded and the network size data feeds have not been enabled). @mrosseel's new pricenode does not supply data still. so add a +75 or so to the final number of nodes for numbers after 2020-08-21. |
KPIs seem to be stable now. I'll use them for the next releases to check if we made progress. Until now because of missing data every now and then I wasn't able to use them for feature/version evaluation. I did use the version update metric a lot which is great to see how quickly our users do update. So from my side this project is now complete. |
here is the grafana config
|
Description
See bisq-network/bisq#3916
Citing essential data points and KPIs for desktop client from issue above
Rationale
If we don't have a baseline and metrics in place to measure our success we'll never be able to tell if some change was a success or a big failure.
As we don't want to include general tracking within the client, which would hurt user privacy, we'll monitor public available information and try to generate as-good-as-it-gets metrics out of it.
Our most important use case is to enable users to buy/sell BTC. Following KPIs help us to measure our success:
Number of active nodes
>Number of available offers
If this conversion number increases compared to the previous timeframe, we either have attracted more market makers or improved the client and enabled the user to create an offer more easily.
To be able to check if we got more market makers on board we could monitor the offerbook to check by how many nodes the offers have been created with. If the ratio
Number of available offers
/Number of nodes
stays roughly the same we can assume that the conversion increase is either by better user targeting in our growth efforts or by improvements within the client.Number of available offers
>Number of trades
As the trade statistics object is published already before the trade is settled (while both parties need to be online) we can't take it as a metric if we improved the trade process itself. If this conversion number increases compared to the previous timeframe, it could mean:
Criteria for delivery
KPIs
Within https://monitor.bisq.network/ it should be possible to select a time frame and app version (or all app versions) and display the KPIs above.
Metrics
Within https://monitor.bisq.network/ it should be possible to select a time frame to show the version spread between active nodes
Tasks
here is the tasks list
- [x] unplanned: fix monitoring daemon (this broke the monitor))- [ ] adapt monitoring daemon to collect trade rate datadeploy new monitoring daemonsourced another metric we already haveEstimates
Based on the numbers posted in bisq-network/bisq#3916 this project will need roughly USD 2200 to deliver this project.
The text was updated successfully, but these errors were encountered: