Introduction
Project Name: Sia heartbeat
Name of the organization or individual submitting the proposal: Michał Maj (individual)
Describe your project.
The goal of the project is to create portal allowing users to register for notification when their hostd node goes down. I am planning on creating the following monitoring channels:
- two independent watchdogs (1 in EU and 1 in US), which will contact nodes via RHPv2 and RHPv3 to check if they are reachable
- optional software to be run on the same machine as hostd, that will send ping messages to these watchdog satellites, allowing for quicker debugging (is the whole machine down or just RHP communication issue?)
Users should be able to register for the following ways of notification:
- E-mail notification
- SMS message
This service is meant to be free. All costs should be covered by grants.
This grant is just for creation of the service and first few weeks of operation. If it succeeds, I will open next grant to secure funds for the service to remain free in long-run.
Who benefits from your project?
Anyone who is running hostd.
How does the project serve the Foundation’s mission of user-owned data?
Self-hosting such watchdogs makes hostd unnecessarily expensive and requires technical knowledge. Providing such portal for free should increase interest in Sia compared to its competitors (who have this feature built-in btw).
Grant Specifics
I estimate project can be up and running for around 2-3 months given I receive total amount of 2500$. This includes:
- VPS for 4 months
- Pack of around 1000 SMS worldwide (we will se how quickly it gets eaten up before next grant)
- Salary for me
Timeline is as follows:
- August - examine what can be extracted from RHP and what’s the best way of doing it (running hostd locally and querying it or maybe custom partial implementation of RHP)
- September - by the end of the month portal should be up and runnning
- October - getting feedback on how it works, improvements. If everything works out - applying for next grant with longer timeframe.
Potential risks that will affect the outcome of the project:
Well, there are only three things that might harm the project:
- My potential lack of time (I am heavily involved into non-technical voluntary work) - the product will be delivered, it just might be a month later.
- Lack of interest from the community
- I am not front-end developer by any means, so portal may come out a little unintuitive. But I will do my best.
Development Information
Will all of your project’s code be open-source? Yes, but I don’t promise there will be documentation on how to run/self-host it (there obviously will be documentation on how to set up additional local watchdog).
Leave a link where code will be accessible for review. GitHub - majudev/hostd-mon
Do you agree to submit monthly progress reports? Yes
Contact info
Email: mimaj@agh.edu.pl
