[bisq-network/roles] Monitoring Operator/Maintainer (#10)

[Harry MacFinned]

### 2019.12 09-15 report - week 50 (0 alerts)
More information and detailed data files are available at : http://lkybpunzakh2wo7d.onion/bisq/

- gaps between fees onion pages : 34 gaps / 2016 pings = 1.7%
In the range. ~ Most gaps were punctual and small. MaxGap = 6

- gaps between prices onion pages : 0 issue, 0 alert transmitted
Only the usual small deviations for DOGE, etc.

- timestamp alerts : 0 issue, 0 alerts transmitted

- fees values : min = 10 s/b : (7573 occurences) : mean = 10.68 s/b : max = 18 s/b (37 occurrences).

Bisq numbers for the week : 102 BTC / 518 trades (= 0.20 BTC/trade)

Exceptions :

Dates | cto | rto | herr | undef | sum |   |
------|-----|-----|------|-------|-----|---
 9 |  37 | 7 | 0 | 4 | **48** 
10 |  29 | 2 | 0 | 3 | **34** 
11 |  65 | 7 | 0 | 6 | **78** 
12 | 317 | 9 | 0 | 9 | **335** 
13 |  29 | 0 | 0 | 4 | **33** 
14 |  22 | 0 | 0 | 3 | **25** 
15 |  17 | 2 | 0 | 4 | **23** 
**sum** | **516** | **27** | **0** | **33** | **576** |

Exceptions by onion :  109 105 116 111 135 sum= 576 
The high exception number is equirepartite because it comes mainly from one long connection issue on my side on 12/12.

- total pings par week = 288 pings per day x 7 days x 5 onions = 10080 pings
- 576 exceptions / 10080 pings = 5.7%.
- 516 cto / 576 exceptions = 89% (cto = connection timeouts)


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/roles/issues/10#issuecomment-565964090
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191216/d5ca4a44/attachment.html>