Luis Helder
Luis Helder
design: https://github.com/HathorNetwork/ops-tools/issues/427 ### Acceptance Criteria - We should make the service return to Prometheus the same count returned by /v1a/status - We should also include in Prometheus the 2 other...
Design: https://github.com/HathorNetwork/ops-tools/issues/433 ### Acceptance Criteria - We should have a metric of number of hits/misses in the cache during execution - We should log the number of cache hits/misses during...
design: https://github.com/HathorNetwork/ops-tools/issues/435 ### Acceptance Criteria - We want to be able to have a metric of network bandwith usage for each peer connection in the fullnodes. - Some other metrics...
We have observed this happening in one fullnode, preventing it from connecting to new fullnodes that got added to the whitelist. We know the loop was halted because the fullnode...
I spotted this error in one of our full-nodes. The log message says what is in the title: `failed to parse whitelist`. There is also this Traceback: ``` Traceback (most...
This is some random behavior we have observed while having a few wallet-headless connected to a fullnode. The wallets are seldomly logging `Ping timeout. Connection is down... { uptime: 4.99,...
I've noticed hathor-core returns 500 when receiving invalid input in the `hexdata` field sent to the `/submit_job` endpoint. We should improve validation on this so it returns 400 instead.
This error happens in the decode_tx api. We should just catch the error and return it in the API. ``` Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/twisted/web/server.py", line 235, in...
We are getting this exception logged as critical level. Maybe we should just treat the error and return in the API. If we want it logged, we should change the...
We should have some treatment for this and log the peer-id from where this is coming.