-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Monitoring Operator/Maintainer #10
Comments
@ManfredKarrer and @mrosseel, I've assigned the two of you to this role, since you have both (somewhat independently) been playing it. We can discuss further what the next steps around monitoring are going to be. Just documenting the current situation for now. |
2018.04 reportWe are still looking for a developer who works on better monitoring tools. The current http://seedmonitor.0-2-1.net/ works pretty reliable regarding false positive reporting but we still have no notifications enabled. Sometimes the stats for the Bitcoin node is not correct (a failing node does not gets reconnected automatically). |
2018.05 reportA few minor issues with some nodes which got quickly recovered. |
2018.05 reportNo issues, no further work is planned except when pricenodes are switched to the new version this will be adapted. This server is shared with the IRC syncing server |
2018.06 report
|
2018.06 reportMonitoring still takes quite of time and attention as notifications are missing. |
@mrosseel, I archived the https://github.com/bisq-network/monitoring repository last month, thinking that this implementation was no longer being used. I understand now that you're keeping your fork at https://github.com/mrosseel/bisq-monitoring up to date operating an instance of it. @ManfredKarrer is also keeping his https://github.com/bisq-network/bisq-monitor repo and instance at http://seedmonitor.0-2-1.net up to date. Are people actually using both solutions? Is there a reason to keep them both going like this? |
Yes https://github.com/bisq-network/bisq-monitor is used as my primary monitoring tool. |
The only reason I'm keeping my instance around is for the better pricenode monitoring (version, sat/b, startup params), the rest is covered by Manfred's monitoring. |
2018.07 reportNo issues occurred that month. |
2018.07 reportNothing to report Note: this server is shared with the IRC syncing server |
Cycle 44 reportRunning monitor.bisq.network
|
Cycle 45 reportRunning monitor.bisq.network
|
Cycle 46 reportRunning monitor.bisq.network
|
Cycle 47 reportRunning monitor.bisq.network
|
Cycle 48 reportRunning monitor.bisq.network
|
Cycle 49 reportRunning monitor.bisq.network
|
Cycle 50 reportRunning monitor.bisq.network
|
Cycle 51 reportRunning monitor.bisq.network
|
Cycle 52 reportRunning monitor.bisq.network
|
Cycle 53 reportRunning monitor.bisq.network
|
Cycle 54 reportRunning monitor.bisq.network
|
Cycle 55 reportRunning monitor.bisq.network
|
Cycle 56 reportRunning monitor.bisq.network
|
Cycle 57 reportRunning monitor.bisq.network
|
Cycle 58 reportRunning monitor.bisq.network
|
This role is responsible for operating @bisq-network monitoring infrastructure and for maintaining any related sources and issues in the https://github.com/bisq-network/monitoring repository.
Team: @bisq-network/monitoring-operators
Docs: https://github.com/bisq-network/bisq/blob/master/monitor/README.md
The text was updated successfully, but these errors were encountered: