71–79 of 79 posts
Earlier quoted context omitted.
true. the way we see it is that we will few use cases with very good UX, and the second thing is to build integrations to all other tools. think of status page that is integrated with all of your observability tools + you can add your own checks.
awesome, good luck!
* rsync photos from phone to NAS (via Termux and Wireguard)
* btrfs-send from desktop to NAS
* restic from NAS to Backblaze
The integration is simple (just a HTTP request) and it notifies me via ntfy.sh and email.
I use a similar service (healthchecks.io) to alert me if my backup jobs haven't succeeded in the past 5 days. * rsync photos from phone to NAS (via Termux and Wireguard) * btrfs-send from desktop to NAS * restic from NAS to Backblaze The integration is simple (just a HTTP request) and it notifies me via ntfy.sh and email.
I really like this idea, but. I've been thinking about this, and also the fact that Pingdom, etc. seem to consolidate. Is there really a big market for "simple monitors"? If you are small, you probably don't care much/do it yourself/don't want to pay. The moment you grow bigger, you have many more comprehensive options available to you like Sentry, Datadog, PD, etc. that offer not only uptime alerts but all kinds of…
A service in a very similar vein is https://healthchecks.io/ - which also provides a nice perspective on how low-effort the setup for a service with a substantial amount of users can be. https://news.ycombinator.com/item?id=31488910 The blog also contains a bunch of useful information and guides around the topic, including various unusual configurations (arduino/esp8266) as well as information on self-hosting.
I've used healthchecks.io for years (and Laravel eco system has some heartbeat checks built into their system), I'm curious how Peeng differs?
If you have any idea what would be make Peeng even more great it'll be cool to hear!
Neat! I definitely read the name as "Peeing" and was confused. (Most people parse words using the first few letters and last few letters when they scan.) The blurb on the site was difficult for me to parse, mentally. It's wordy and awkward with the negative in there: > Receive an HTTP request whenever your heartbeat endpoint is not pinged for a configured interval of your choice. "Get POSTed when your endpoint stops…
Now I can't unsee "peeing"
Earlier quoted context omitted.
There was a site/service called gnip. https://en.m.wikipedia.org/wiki/Gnip
Man gnip was wild. I remember getting access to the Twitter firehouse for a while through this service. We built some really useful stuff with this.