Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Monitoring Operator/Maintainer #10

Open
cbeams opened this issue Sep 4, 2017 · 180 comments
Open

Monitoring Operator/Maintainer #10

cbeams opened this issue Sep 4, 2017 · 180 comments
Assignees
@Emzy
Labels
team:dev https://bisq.wiki/Dev_Team team:ops https://bisq.wiki/Ops_Team

Comments

@cbeams
Copy link
Member

cbeams commented Sep 4, 2017 •
edited
Loading

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
@cbeams cbeams changed the title network monitor operator and maintainer Monitoring Operator/Maintainer Jan 2, 2018
@cbeams
Copy link
Member Author

cbeams commented Jan 2, 2018

@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.

@cbeams cbeams added role and removed role:op labels Jan 3, 2018
@ManfredKarrer
Copy link
Member

ManfredKarrer commented May 1, 2018 •
edited
Loading

2018.04 report

We 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).

@ManfredKarrer ManfredKarrer mentioned this issue May 1, 2018
Closed
@cbeams cbeams removed the a:role label May 4, 2018
@cbeams cbeams mentioned this issue May 8, 2018
Closed
@ManfredKarrer
Copy link
Member

2018.05 report

A few minor issues with some nodes which got quickly recovered.

@ManfredKarrer ManfredKarrer mentioned this issue May 30, 2018
Closed
@mrosseel
Copy link
Member

mrosseel commented Jun 1, 2018

2018.05 report

No 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

bisq-network/compensation#80

@mrosseel mrosseel mentioned this issue Jun 1, 2018
Closed
@mrosseel mrosseel mentioned this issue Jun 29, 2018
Closed
@mrosseel
Copy link
Member

2018.06 report

  • the new expected pricenode version (0.7.1-SNAPSHOT) was set in the monitoring, all pricenodes now run this version so no pricenode is in error at the moment.
    This server is shared with the IRC syncing server

bisq-network/compensation#83

@ManfredKarrer ManfredKarrer mentioned this issue Jun 30, 2018
Closed
@ManfredKarrer
Copy link
Member

2018.06 report

Monitoring still takes quite of time and attention as notifications are missing.

@cbeams
Copy link
Member Author

cbeams commented Jul 3, 2018

@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?

@ManfredKarrer
Copy link
Member

Yes https://github.com/bisq-network/bisq-monitor is used as my primary monitoring tool.

@mrosseel
Copy link
Member

mrosseel commented Jul 4, 2018

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.

@ManfredKarrer ManfredKarrer mentioned this issue Jul 26, 2018
Closed
@ManfredKarrer
Copy link
Member

2018.07 report

No issues occurred that month.

/cc bisq-network/compensation#93

@mrosseel mrosseel mentioned this issue Jul 31, 2018
Closed
@mrosseel
Copy link
Member

2018.07 report

Nothing to report

Note: this server is shared with the IRC syncing server

bisq-network/compensation#105

@ManfredKarrer ManfredKarrer mentioned this issue Aug 30, 2018
Closed
@Emzy Emzy mentioned this issue Feb 6, 2023
Closed
@Emzy
Copy link

Emzy commented Feb 6, 2023

Cycle 44 report

Running monitor.bisq.network

  • OS updates
  • minor Grafana upgrade

/cc bisq-network/compensation#1232

@Emzy Emzy mentioned this issue Mar 8, 2023
Closed
@Emzy
Copy link

Emzy commented Mar 8, 2023

Cycle 45 report

Running monitor.bisq.network

  • OS updates
  • minor Grafana upgrade

/cc bisq-network/compensation#1252

@Emzy Emzy mentioned this issue Apr 11, 2023
Closed
@Emzy
Copy link

Emzy commented Apr 11, 2023

Cycle 46 report

Running monitor.bisq.network

  • OS updates
  • mayor Grafana upgrade
  • increase JAVA process memory and restart JAVA process

/cc bisq-network/compensation#1280

@Emzy Emzy mentioned this issue May 13, 2023
Closed
@Emzy
Copy link

Emzy commented May 13, 2023

Cycle 47 report

Running monitor.bisq.network

  • OS updates

/cc bisq-network/compensation#1296

@Emzy Emzy mentioned this issue Jun 17, 2023
Closed
@Emzy
Copy link

Emzy commented Jun 17, 2023

Cycle 48 report

Running monitor.bisq.network

  • OS updates

/cc bisq-network/compensation#1320

@Emzy Emzy mentioned this issue Jul 17, 2023
Closed
@Emzy
Copy link

Emzy commented Jul 17, 2023

Cycle 49 report

Running monitor.bisq.network

  • OS updates

/cc bisq-network/compensation#1336

@Emzy Emzy mentioned this issue Aug 22, 2023
Closed
@Emzy
Copy link

Emzy commented Aug 22, 2023

Cycle 50 report

Running monitor.bisq.network

  • OS updates

/cc bisq-network/compensation#1363

@Emzy Emzy mentioned this issue Sep 20, 2023
Closed
@Emzy
Copy link

Emzy commented Sep 20, 2023

Cycle 51 report

Running monitor.bisq.network

  • OS updates

/cc bisq-network/compensation#1383

@Emzy Emzy mentioned this issue Oct 21, 2023
Closed
@Emzy
Copy link

Emzy commented Oct 21, 2023

Cycle 52 report

Running monitor.bisq.network

  • OS updates

/cc bisq-network/compensation#1402

@Emzy Emzy mentioned this issue Nov 19, 2023
Closed
@Emzy
Copy link

Emzy commented Nov 19, 2023

Cycle 53 report

Running monitor.bisq.network

  • OS updates

/cc bisq-network/compensation#1416

@Emzy Emzy mentioned this issue Dec 22, 2023
Closed
@Emzy
Copy link

Emzy commented Dec 22, 2023

Cycle 54 report

Running monitor.bisq.network

  • OS updates

/cc bisq-network/compensation#1441

@Emzy Emzy mentioned this issue Jan 24, 2024
Closed
@Emzy
Copy link

Emzy commented Jan 24, 2024

Cycle 55 report

Running monitor.bisq.network

  • updates

/cc bisq-network/compensation#1469

@Emzy Emzy mentioned this issue Feb 25, 2024
Closed
@Emzy
Copy link

Emzy commented Feb 25, 2024

Cycle 56 report

Running monitor.bisq.network

  • updates

/cc bisq-network/compensation#1492

@Emzy Emzy mentioned this issue Mar 26, 2024
Closed
@Emzy
Copy link

Emzy commented Mar 26, 2024

Cycle 57 report

Running monitor.bisq.network

  • updates

/cc bisq-network/compensation#1504

@Emzy Emzy mentioned this issue Apr 28, 2024
Open
@Emzy
Copy link

Emzy commented Apr 28, 2024

Cycle 58 report

Running monitor.bisq.network

  • updates

/cc bisq-network/compensation#1537

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Emzy Emzy

Labels
team:dev https://bisq.wiki/Dev_Team team:ops https://bisq.wiki/Ops_Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@ripcurlx @wiz @cbeams @freimair @Emzy @ManfredKarrer @mrosseel