What can I monitor with PulseBeacon?
Heartbeat/cron jobs, HTTP endpoints, keyword/content checks, SSL certificates, TCP ports, and server agent metrics.
What does “Confirming…” mean on a monitor?
A probe just failed and PulseBeacon is re-checking before deciding anything. It is not an outage: no alert has been sent, uptime is unaffected, and status pages keep showing the last confirmed state. If the failure repeats on consecutive probes (3 by default) the monitor becomes Down; if a re-check succeeds, the blip is logged as a transient failure and nothing alerts.
Will I get an alert for every failed probe?
No. Alerts fire only on confirmed state transitions: one DOWN alert when an outage is confirmed, one recovery alert when the monitor is confirmed healthy again. Duplicate transitions are deduplicated across all channels.
Why does a heartbeat monitor show late/down?
PulseBeacon did not receive a ping within the expected window plus grace — the next interval for interval mode, or the next scheduled run (in your timezone) for cron mode. Confirm your scheduler/cron is running, the job exits successfully, and the ping URL is called after success.
Can I monitor SSL and ports too?
Yes. SSL checks track expiry and validity; port checks verify TCP reachability for host:port combinations.
My custom domain is stuck in pending state. What should I check?
Validate CNAME target first, then add TXT/DCV records exactly as shown in PulseBeacon (if requested). DNS propagation + SSL issuance can take time; re-run verify after propagation.
Why am I not receiving alerts?
- Integration may be disabled.
- Rule may not include the event type you expect.
- Rule scope may not match the resource.
- Email/webhook provider response may be failing (use Integration Test).
What is the difference between hosted and custom-domain status pages?
Hosted pages use /status/{slug} on your PulseBeacon app domain. Custom-domain pages serve from your verified subdomain root (for example https://status.customer.com/).
How do plan limits affect monitors?
Limits control quantity and speed (checks, servers, status pages, minimum interval, custom domains, retention windows). Existing data is preserved on downgrade, but new creation may be blocked while over-limit.