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

Harry MacFinned notifications at github.com
Mon Nov 25 08:26:48 UTC 2019


### 2019.11 18-24 report - week 47 (0 alert)
More information and detailed data files are available at : http://lkybpunzakh2wo7d.onion/bisq/

- gaps between fees onion pages : 67 gaps / 2016 pings = 3.3%
In the range. ~ Most gaps were punctual and small. MaxGap = 8

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

- timestamp alerts : 0 issue, 0 alert transmitted

- fees values : min = 10 s/b : (6448 occurences) : mean = 12.83 s/b : max = 28 s/b (79 occurrence).

Bisq numbers for the week : 158 BTC / 645 trades

Exceptions :

Dates | cto | rto | herr | undef | sum |   |
------|-----|-----|------|-------|-----|---
18 | 58 | 0 | 0 | 1 | **59** 
19 |  8 | 1 | 0 | 1 | **10** 
20 | 39 | 0 | 0 | 5 | **44** 
21 | 50 | 1 | 0 | 3 | **54** 
22 | 47 | 2 | 0 | 0 | **49** 
23 | 66 | 1 | 0 | 4 | **71** 
24 | 25 | 0 | 0 | 4 | **29** 
**sum** | **293** | **5** | **0** | **18** | **316** |

Exceptions by onion :  55 51 81 72 57 sum= 316 

- total pings par week = 288 pings per day x 7 days x 5 onions = 10080 pings
- 316 exceptions / 10080 pings = 3.1%.
- 293 cto / 316 exceptions = 92.7% (cto = connection timeouts)

Among the 316 exceptions this week, roughly 80 exceptions came from my monitoring side.
The other exceptions came from the network and did concern all nodes in an equirepartite way.

-- 
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-558045287
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191125/fad749ef/attachment.html>


More information about the bisq-github mailing list