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

[Harry MacFinned]

# 2018.09 Report - Prices monitoring

Reminder :
Python croned task monitoring the Bisq network onion nodes for the prices. On a 5 minutes basis.
All requests have a 10 seconds timeout, ie if the onion node doesn't answer in 10 seconds, the request is abandoned. Generally nodes answer in less than 1 second.

Prices are not archived.

The monitoring is at the moment realized by writing alerts in files + sending emails.

**The prices monitoring runs only since september 16th.**


### Timeouts
Not enough data and not well enough recorded to make a good analysis.
Please see the report on fees to have a better figure.


### Divergence between nodes
atm, the pricenodes delivers 198 prices 99.x% of the time.
But, on rare cases, it's also 197 or 199.

The threshold to trigger divergence detection is 5%.
ie, for each asset, for all the pricenodes, when relGap = [max(prices)-min(prices))/max(prices] > 0.05
the divergence is recorded.
And if it concerns a usually traded asset, an email is sent.

There are a bunch of few-traded assets (PASC, XIN), with small values, which easily trigger alerts, specifically due to their small values.

There was only one noticeable issue detected for the second half of september:
2018-09-26 19:16 to 19:30 : concerned all prices. One node delivered a 0 price for all prices (or was in timeout).
This issue lasted less than 15'. That's why I didn't relay it on the slack.

There were 7 other punctual alerts, but seemed to be all false positives artifacts due to monitor bad code (I wrongly assumed the nodes delivered always the same number of prices).

### Other

There was an issue with XMR prices on sept 3rd
https://bisq.community/t/huge-disparity-in-market-price-for-xmr/6107
The price monitor runs only since sept 16th, so sorry but I have no data to investigate in details if it was a pricenode divergence or if the issue was upstream.

A user mentionned a (persistent) issue with CAD prices
https://bisq.community/t/prices-provided-by-bitcoin-average-market-price-provider-are-out-of-wack-for-cad/6215
The price monitor related nothing being due to a divergence in pricenodes for CAD.
It seems to be purely a local/global price issue on the provider side.


### Prices statistics
None atm.


### Improvements
- Some alerts could be automaticaly directed to the slack.
- the timeouts can be better analyzed
- treat correctly some cases which actually generate false positives
- ... 


-- 
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-425444152
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180928/44d1d715/attachment.html>