[bisq-network/proposals] Add bonus payment for seed nodes operators when node has 99.9% availibility (#102)

Florian Reimair notifications at github.com
Fri Jul 19 09:54:58 UTC 2019

Since we are confronted with a lot of guesswork when a seed node is offline, a more professional monitoring system would benefit the cause as well.

I therefore suggest to **add setting up a system health reporting system to be a mandatory requirement for compensation** or something alike. (@ManfredKarrer maybe you want to add that to your proposal?)

I went forward and got such a system up and running for our monitor ([live](https://monitor.bisq.network/d/UMQdVnNWz/server-metrics-collectd)):
![Screenshot from 2019-07-19 11-23-36](https://user-images.githubusercontent.com/1070734/61524906-b938fc00-aa17-11e9-8990-160942c50977.png)

This example is [collectd](https://collectd.org/) collecting information every 30 seconds on the monitor server itself and sending it to the grafana database. The JVM heap space is gathered from the [bisq monitor process](https://github.com/bisq-network/bisq/tree/master/monitor), everything else is gathered from the OS. These metrics can all be gathered without the need to change the bisq code. It is minimal effort to setup (I guess 1h of your time) and collectd is made for heavy load environments so we do not loose a great amount of computing power. All in all, we would gain the ability to correlate seed nodes going offline with their system health (excessive CPU usage, out of memory, bandwidth limitations, ...) and maybe take a lot of guesswork out of our debugging efforts.

I am currently working on getting the monitor ready for such input and piecing together a readme on how to make collectd talk to the monitor. I would then integrate that into the [How to seednode](https://docs.bisq.network/exchange/howto/run-seednode.html) guide for everyone to see when the time comes.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190719/4a07b822/attachment.html>

More information about the bisq-github mailing list