Introducing Sigabrt.dev: A Cronjob Monitor via SSH TUI

sigabrt is designed to ensure you are notified the exact moment a critical service ceases to function.

Note: This project is currently a work in progress.

🛠️ How it Works

Setting up monitoring is a simple two-step process:

• Step 1: Define your endpoint. Give it a name, specify the expected reporting frequency, and set a "grace period" for how long the system should wait before flagging it as down.
• Step 2: Integrate the pulse. Append a single curl command to the end of your existing script to signal success.

Implementation Example

If you have a backup script running nightly, your crontab would look like this:

# Run backup at 3:00 AM daily
0 3 * * * ./backup.sh && curl -fsS https://sigabrt.dev/pulse/8f3c.../beat nightly-backup

The Logic of a "Pulse"

The system monitors the time elapsed since the last signal. A service is considered $\text{down}$ if: $\Delta t > (\text{Interval} + \text{Grace Period})$

---

🖥️ The SSH Terminal Interface

Instead of a traditional web dashboard, you can manage and view your endpoints directly from your terminal.

Access Instructions:

1. Add your SSH public key to the settings.
2. Connect via: ssh sigabrt.dev

Early Days Warning: The TUI is currently fully interactive read-only and will evolve as the project grows.

TUI Status View

When you connect, you'll see a layout similar to this:

↑↓ select · enter events · q quit

---

🔔 Features & Pricing

Stop guessing if your jobs ran. Get definitive proof.

• Alerting: Receive notifications via Email and/or ntfy when a status changes.
• History: Access a log of pulses and status shifts for up to 90 days.
• Flexibility: Intervals can be set from one minute upwards.

Pricing Model

Sigabrt offers a straightforward approach:

• Free Tier: Start here to test the waters.
• Paid Tier: One flat price for:
  • $\infty$ Endpoints
  • $\infty$ Heartbeats
  • Full 90-day history

Upgrade your account once you're monitoring something you simply cannot afford to lose.