pozhidaevak / antpool-monitor Goto Github PK

View Code? Open in Web Editor NEW

3.0 3.0 3.0 137 KB

It monitors hashrate of antpool workers and sends messages to notify if any worker has stoped

Java 96.90% Shell 3.10%

antpool-monitor's People

Contributors

Stargazers

Watchers

Forkers

teerawatxxx gtr-golf

antpool-monitor's Issues

requestWorkers method is invoked twice at the start of the application

According to logs requestWorkers() is called twice at the start of the app.

2018-01-06 19:34:39,677 [INFO] g.a.a.AntpoolApi [hystrix-AntpoolApi-1] Starting requestWorkers
2018-01-06 19:34:39,677 [INFO] g.a.a.AntpoolApi [hystrix-AntpoolApi-2] Starting requestWorkers

It should be called only once.

Support multiple antpool sub-accounts

For now, only one antpool account is supported.
It would be great to support several accounts. For this antpool property in application-secrets.yaml should support lists like this:

antpool:
  - key: "key1"
    secret: "secret1"
    user: "user1"
  - key: "key2"
    secret: "secret2"
    user: "user2"

Tests from MonitorTest fail intermittently

MonitorTest class has tests that check how Circuit Breaker logic will be working. However, they have intermittent fails. The failures are probably connected with Hystrix or the way it is used.

Excessive messages are sent if antpool is not responding correctly

A lot of messages are sent to telegram if antpool is not returning correct response.
Probably some logic needs to be implemented to stop requests to antpool for sometime after receiving an incorrect response.

Recommend Projects