[bisq-network/bisq-monitor] 2018.08 Report : Fee monitoring (#11)

[Chris Beams]

> If I'm on the wrong place for this report, apologies, and just tell me.

This is the wrong place. There is a Monitoring Operator / Maintainer role at https://github.com/bisq-network/roles/issues/10.

I'm not sure what value this work provides if it's not providing alerts to @bisq-network/pricenode-operators. Ideally this would happen via messages coming into the #pricenode channel in Slack, which all operators should have notifications turned on for.

False positives have been a big problem in the past, and have been the reason previous monitoring solutions have been scrapped. Please make sure that what you're building is going to be of actual value before investing much more into it. I recommend engaging with the operators to see what they actually need and want. A good example would be: how could we have caught the BitcoinAverage outage and the stale prices that ensued earlier this week? I just happened to see it as it was occurring, but it would have been excellent to have an alert telling us that our pricenodes were off.

In any case, please close this issue. Thanks.

-- 
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/bisq-monitor/issues/11#issuecomment-418397760
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180904/c1c3e7c4/attachment.html>