Title: Hey folks! Shahar and Tal from Keep (<a href="https:&#x2F;&#x2F;www.keephq.dev">https:&#x2F;&#x2F;www.keephq.dev</a>) here!<p>For the last few weeks we’ve been building Peeng and can now share our beta with you: <a href="https:&#x2F;&#x2F;www.peeng.sh" rel="nofollow noreferrer">https:&#x2F;&#x2F;www.peeng.sh</a>. Peeng is the easiest and quickest “heartbeat” architecture we could think of. Just pick a subdomain (e.g. x.peeng.sh), configure an interval, an endpoint, and a payload, and hit that subdomain every &lt;X (interval) seconds — If you won’t, Peeng will send an HTTP POST request to your configured endpoint.<p>It’s Pingdom&#x2F;Cronitor&#x2F;heartbeat.sh free alternative (but the other way around and A LOT simpler, with a lot more capabilities), suitable for developers, system administrators, DevOps, and individuals with complex networking situations (think “onprem” or K8s clusters with no inbound).
Instead of inbound heartbeat checks — Peeng presents outbound heartbeat checks!<p>Quick demo: <a href="https:&#x2F;&#x2F;youtu.be&#x2F;ZX5mrnMRCwU" rel="nofollow noreferrer">https:&#x2F;&#x2F;youtu.be&#x2F;ZX5mrnMRCwU</a><p>Why we built this:<p>- We needed an easy way to let Keep (<a href="https:&#x2F;&#x2F;github.com&#x2F;keephq&#x2F;keep">https:&#x2F;&#x2F;github.com&#x2F;keephq&#x2F;keep</a>) customers behind closed networks monitor their Keep instance
- We needed an easy &amp; quick way to setup monitoring for our cronjobs
- We wanted to give people with complex networking situations (e.g. behind a firewall) an easy way to monitor their services&#x2F;processes<p>The beta version lets you:<p>- Create 5 endpoints for free
- Configure the endpoint and the payload to be sent when the subdomain is not hit
- See the visits (every HTTP GET request to your subdomain) and requests (every HTTP POST sent to your configured endpoint)
- Secret header (x-peeng-secret) that confirms requests are made by you<p>What’s next:<p>- A status page that displays your subdomains and their health together with embeddable status blocks that allow you to display the status of an endpoint in your web page (you can also send query params when sending the GET requests that will be included)
- Rest API (for subdomain creation, beats retrieval, etc., imagine curl -X POST peeng.sh&#x2F;subdomain -H API_KEY —json {”subdomain”: “hn”, “endpoint”: “<a href="https:&#x2F;&#x2F;..”" rel="nofollow noreferrer">https:&#x2F;&#x2F;xn--ivg</a>, “payload”: {…}})
- Hierarchy-based subdomains that allow you to create a nested heartbeat solution (i.e. dynamically create a heartbeat subdomain under x.peeng.sh → y.x.peeng.sh, z.x.peeng.sh)<p>This is still very early, so we’d love to hear your feedback and opinions. We’re open to any feature request, so just reach out via Intercom :)
Upvote: