I wrote a software like this, tried to ship it but I failed. Now it's open-source for everyone.
If you're interested, grab it.
41–50 of 65 posts
I wrote a software like this, tried to ship it but I failed. Now it's open-source for everyone.
If you're interested, grab it.
btw, the ping engine is a Go app that pings each hosts in a separate goroutine. I might open source it in the future once the code has more tests and less shame.
Earlier quoted context omitted.
Too expensive... Why all monitor services charge so much for so simple service?
It's not as simple as you'd think. Monitoring 1 website is easy, monitoring 1M websites and gathering results in realtime from stations around the globe to make a proper decision is a different thing. Significant bandwidth, and CPU are needed to achieve this, not to mention relying on third party services like twilio and sendgrid to notify customers and that cost money too.
This is awesome but what is the motivation behind this? Why do you care to set up a server and pay for the (minimal) bandwidth that is needed for this service? Is this purely an act of goodwill? Do you hope that this will gain traction so that you can start charging for the service? Are you secretly harvesting clusters of IP addresses of HN readers?
Good question! I think most of us with pet projects do it either to learn something or with the hopes of gaining a lot of traction and one day implement some paid feature. For me it was both. Maybe one day if there are a lot of users I'll implement paid accounts with more than 10 alerts and history dashboard. But most likely it will never gain enough traction for that, in which case it's no problem, since I have 6 ti…
It feels great to hack on something like this, and not worry about billing integration and supporting paid customers at first.
Earlier quoted context omitted.
haha, there is if I ever want to get another programming job! It's bad, trust me. The ping function is just a retouched version of Go's icmp test: https://github.com/golang/go/blob/master/src/net/ipraw_test.... and that's the _good_ part.
I wouldn't worry too much about it. Everybody writes horrible duct-tape code at some point, and showing how you improved/refactored the code is a much nicer thing than showing how you supposedly magically got it right the first time :)
How to stop?