playing for KEEPS
Contributor Profile
@enzy_me#2558
PFK Rewards
Round 5
@enzy_me#2558
3000
3k KEEP. ​https://keepnodes.xyz/​​​
Round 4
@enzy_me#2558
2000+
Tier Two (2k-5k KEEP)
Introduce yourself
Hi. My name is Aleksandr.
Nodes
0x9b7126BC3Ab1A2343BF9ea4d09fB9C290955826c
0x5607C1bF6D0DE1aD494306af79A60bCD7fbbb9F8
Contribution
31.10.2020

Here is my PFK submission for October.

I have updated my site for keep nodes monitoring https://keepnodes.xyz/
Now any user can add his node to monitoring in one command - https://keepnodes.xyz/how-to.
Also we could see the user location on the map https://keepnodes.xyz/map.
All ip addresses are masked in logs and coordinates are rounded as it is sensitive information. There is a new tab  https://keepnodes.xyz/errors.

Here we can observe errors that could appear. Users can suggest their errors and it's solution or try to find solution that already exist.
Also we could watch latest logs to help other person to solve his problem.
I running BEACON and ECDSA nodes online.
Thank you.


01.10.2020

I see a lot of questions in keep chats about how to monitor runnnigs nodes: is it all ok? That is why I decided that it will be usefull to implement such tool. Presented tool uses docker containers logs. It seems that there is no any sensitive information in logs, that is why I decided that this type of monitoring is allowed.
Here is a site http://keepnodes.xyz/ for keep nodes monitoring.

I have used following tools :
docker-logger (https://github.com/umputun/docker-logger) that is attached to desired container and transfer logs via UDP to elastic server 
  • logstash to parse and prepare logs 
  • elastic server as a log storate 
  • separate worker for log analyze
  • simple front to visualize the node status and to showing these logs 
There is only one test node, but I will try to involve other keepers to participate in this project. ]

TODO:
  • modify the docker-logger to make the installation in click 
  • implement alerting 
  • live log update 

I running
BEACON and ECDSA nodes online at the address 0x9b7126BC3Ab1A2343BF9ea4d09fB9C290955826c
and test BEACON node at 0x5607C1bF6D0DE1aD494306af79A60bCD7fbbb9F8.



31.08.2020

Last week I have tried to implement KEEP pool application that let small KEEP holders pool and run a node. It's just a prototype without ethereum interaction.
This application consists of two parts:
  • telegram bot to create and enter pools
  • utility site to interact with ethereum blockchain and sign the transactions (now it's mocking) 
The prototype is written as a monolithic application with symphony. I will try to realize all the remaining points to became the full value project.

I running BEACON and ECDSA nodes online at the address - 0x9b7126BC3Ab1A2343BF9ea4d09fB9C290955826c.
Github - https://github.com/troo/keep_pool
Telegram Bot - @keep_pool_bot
Contribution: KEEP Tools
Contribution: KEEP Guides
Contribution: Community Resources