About 5 min
Heartbeat monitoring
Your app, bot, or automation sends a “still alive” signal so silent failures get caught.
What it is
A heartbeat means your program calls a ping URL on a schedule. vibePulse only asks: “did a ping arrive within the interval?” — not whether a page returns 200, but whether your code is still running.
Real examples
- 1
Discord or Telegram bot (24/7 VPS)
When the bot process dies, nobody gets replies. Send a ping every 10 minutes and get alerted soon after the bot stops.
- 2
Python or Node automation script
Scripts on while loops or schedulers — hourly crawls, stock checks, reports. Catches cases where cron survived a reboot but the main script did not.
- 3
Self-hosted n8n or Make workflows
Automations on a home PC or small VPS — avoid discovering failure days after “it worked yesterday”.
- 4
Vibe-coded MVP (Railway, Fly.io, Render)
Deploy is easy but no health URL, or the web tier is up while the queue worker is dead. One heartbeat line proves the server process is alive.
- 5
AI agent, trading, or alert bot
API polling loops and long-running agents. If the loop dies after a network error, stopped pings alert you immediately.
How to connect
- Create a Heartbeat monitor in the dashboard and copy the ping URL.
- Set `VIBEPULSE_PING_URL` and paste install code into your bot or script.
- Match the monitor interval with the sleep/interval in code.
- When the first ping appears on the dashboard, you are done. → See Getting started in the sidebar