Skip to content
HN On Hacker News ↗

sigabrt — know when your service stops

▲ 81 points • 35 comments • by 4815162342 • 3w ago • HN discussion ↗

Pangram verdict · v3.3

We believe that this entire text is AI.

97 %

AI likelihood · overall

AI
0% human-written 100% AI-generated
SEGMENTS · HUMAN 0 of 1
SEGMENTS · AI 1 of 1
WORD COUNT 223
PEAK AI % 97% · §1
Analyzed
Sep 20
backend: pangram/v3.3
Segments scanned
1 windows
avg 223 words each
Distribution
0 / 100%
human / AI fraction
Verdict
AI
Pangram v3.3

Article text · 223 words · 1 segments analyzed

Human AI-generated
§1 AI · 97%

ssh sigabrt.dev Work in progress Know the moment your service stops running. Your script pings a URL when it finishes. If the ping doesn't arrive on schedule, sigabrt emails you. 10 heartbeats free. No card required. nightly-backup · every 24h · 15m grace Mon — Thu three nights of pulses, right on time Thu 03:15 — nothing arrived. Email sent. 01 Create an endpoint Name it, say how often it should report in, and how long you'll forgive it. You get a ping URL. 02 Add one line to the job A curl at the end of your script, after the work succeeds. No agent, no library, no credentials. 03 Forget about it Silence means it's fine. You only hear from us when a pulse doesn't arrive. In your terminal Work in progress Endpoints over SSH Add your SSH public key in settings, then connect. Every endpoint’s status, schedule and recent events in your terminal. Early days: it only reads for now, and it will change as it grows. Tell us what you’d want from it. Alerts Email and/or ntfy on status changes History Pulses and status changes Interval From one minute upward, with a grace period One price. Unlimited endpoints, unlimited heartbeats, 90 days of history. Start on the free tier and upgrade when it's carrying something you'd miss. €15 / month