How do shared monitor allowances work?

To prevent a momentary network blip from paging your on-call engineer:

• Consecutive Failure Thresholds: On each alert channel, set how many consecutive checks must fail before an alert is sent (for example, 1 failure for critical payment endpoints, or 2–3 consecutive failures for standard pages).
• Maintenance Windows: Schedule maintenance windows during planned deployments or server upgrades to mute notifications until your work is complete.

Acumen Logs WHOIS & Domain Monitoring checks your domain registration every two days, and daily once expiry is within a month:

• What is stored: Each check records the domain expiry date, registrar, and name servers (plus a DNS diff).
• When reminders are sent: Expiry warnings go out at 45 days, 30 days, and on each daily check inside 14 days. Registrar, owner, and name-server changes are stored in the history and do not send an alert.

For a one-off lookup without an account, use our free RDAP check tool or free WHOIS lookup tool.

Acumen Logs SSL Monitoring reads your certificate on the first check and then checks it about once a day:

• Expiry Reminders: Sent at 45 days and 30 days before expiry, and then on every daily check once 14 days or fewer remain (or on a custom day, week, or month schedule per alert channel).
• Trust & Hostname Alerts: A hostname mismatch or certificate verification failure (expired, self-signed, or untrusted issuer) triggers an immediate alert when detected.

You can also run an instant one-off check anytime with our free SSL certificate checker.

Heartbeat monitors count towards the same plan allowance as uptime, API, SSL, WHOIS and RUM monitors. The total shared allowance on each plan is:

• Free Plan ($0/mo): 10 monitors, with email alerts
• Solo Plan ($5/mo): 100 monitors, with email, Slack, Microsoft Teams, desktop and webhook alerts
• Essentials Plan ($39.99/mo): 150 monitors
• Pro Plan ($149.99/mo): 200 monitors

For example, four uptime monitors and six heartbeat monitors use the full Free allowance. See more shared allowance examples.

Compare plan allowances on the pricing page.

With Acumen Logs Heartbeat Monitoring, you create a unique check-in URL and set the expected interval (such as every hour or once a day). At the end of your cron job, database backup, or queue worker, your script sends a single HTTP request (GET, POST, or HEAD) to that URL.

One interval runs from the last ping. A ping that arrives after the interval is marked late in your history. If no ping arrives within the interval, the monitor is marked failed and a missed alert is sent. There is no agent or SDK to install.

To prevent silent webhook or integration failures:

1. Endpoint & Payload Checks: Configure an API monitor to send scheduled POST or GET requests with test headers to your webhook receiver URL and assert a 200–299 response within your latency budget.
2. Background Queue Heartbeats: If your webhook handler pushes events onto a background queue, add a heartbeat check at the end of your worker job so you are alerted if the queue processor stalls.