Use two complementary checks: an external HTTP(S) monitor for each public page or endpoint, and a heartbeat monitor that expects a success-only ping from every important scheduled job. The first tells you whether users can reach and use your site; the second tells you whether a backup, sync, report, renewal, or cleanup task actually ran. Define success, choose an interval and grace period that match the job, send alerts to a channel someone watches, and suppress planned maintenance so normal work does not become a false incident.
Choose the check that answers your question
A website monitor initiates a request from outside your infrastructure. It can test availability, response time, TLS or domain expiry, and (when supported) page content. A heartbeat reverses the direction: the scheduled process calls a unique URL only after successful completion. If that call is late or absent, the monitor alerts. UptimeRobot describes this as “cron job monitoring, also called heartbeat monitoring,” for checking whether scheduled tasks and background jobs run on time.
| Risk | Use | What a failure means |
|---|---|---|
| Public site, API, login, checkout | HTTP(S) check, plus keyword or transaction assertion when needed | An outside user cannot reach the service or receives an unacceptable response |
| Backup, report, data sync, SSL renewal, email delivery, cache rebuild, cleanup | Heartbeat (success-only ping) | The job did not start, exited early, overlapped incorrectly, or finished too late |
| Regional access | Checks from more than one monitoring location | Reachability differs by geography or network |
Build a reliable website monitor
1. List user-critical URLs
Begin with the home page, public API endpoints, authentication page, checkout or payment path, and any endpoint whose failure has a direct business consequence. Give each monitor an owner and a name that identifies environment and function, such as production—checkout—POST health.
2. Define success beyond status code
An HTTP 200 response is not proof that an application works: an error page can be returned with a friendly 200 status. Use a keyword/content assertion when a particular phrase must appear, or a browser/transaction check when the path requires form submission, a session, or several steps. Keep the assertion narrow and stable so harmless copy changes do not page the team.
Recommended Free Tools
#1 Best Overall
- WIFI ENABLED TO CONTROL FROM ANYWHERE – Transform your home into a smart home with the Feit Electric Smart Wi-Fi Plug. Remotely turn on or off lights, fans, coffee makers, or other home appliances from your smartphone or tablet. Works seamlessly with Alexa and Google Home, giving you effortless voice control without needing a separate hub. Manage your devices anytime, whether you’re at home, at work, or traveling.
- SIMPLE SETUP, NO HUB REQUIRED – Enjoy the convenience of smart home automation without extra equipment. The plug connects directly to your 2.4 GHz Wi-Fi network, making installation fast and easy. Plug it in, download the Feit Electric app, follow the simple steps, and your devices are instantly connected. Perfect for beginners or anyone looking to expand their smart home ecosystem with minimal hassle.
- SET YOUR ROUTINE & SAVE ENERGY – Save energy, stay organized, and automate daily routines with customizable schedules and timers. Set your lamps, heaters, or appliances to turn on and off automatically at specific times, ensuring your home is always comfortable and efficient. Ideal for morning routines, evening wind-downs, or holiday lighting, giving you peace of mind and energy savings without constant manual operation.
- ENHANCED SAFETY & CONVENIENCE – Protect your home and appliances with the Feit Electric Smart Plug’s durable design and safety features. Its compact size fits easily into standard indoor outlets without blocking other sockets. With real-time app control and notifications, you can monitor appliance activity and prevent energy waste. Ideal for families, pet owners, or anyone seeking a smarter, safer, and more convenient home setup.
- RELIABLE 2.4GHz WI-FI PERFORMANCE – Designed to work exclusively on 2.4 GHz networks, this smart plug provides stable connectivity for smooth operation of all your devices. Avoid interruptions caused by incompatible networks, ensuring your appliances respond instantly when controlled via the app or voice commands. Perfect for indoor home use, it supports up to 15 amps, handling heavy-duty appliances safely and reliably.
3. Measure the signals that matter
- Record response time and alert on a threshold appropriate to the endpoint.
- Monitor certificate and domain expiry where your service supports those checks.
- Use multiple monitoring locations when customers are geographically distributed or a single network path is not representative.
- Check APIs with an authentication method that does not expose a production secret in a public URL; rotate credentials according to your normal security policy.
4. Route and repeat alerts
Send notifications to an actively watched email address or integration. Include the monitor name, URL, expected check time, observed status or content result, and the last successful check. Configure recurring reminders for unresolved incidents and an escalation path rather than an endless stream of identical messages.
5. Protect your history from planned work
Create a maintenance window before deployments, migrations, or an intentional job pause. A maintenance window prevents expected downtime from polluting uptime statistics and keeps on-call staff from chasing a known event. Remove or shorten the window when the work finishes.
Monitor cron and other scheduled jobs with a heartbeat
1. Select jobs whose absence matters
Prioritize tasks where one missed run creates material risk: backups, report generation, data synchronization, certificate renewal, email delivery, cache rebuilds, and cleanup scripts are typical examples.
2. Create a monitor with an interval and grace period
Set the expected check-in interval from the job’s normal schedule, then add enough grace for ordinary runtime variation and queue delays. The monitor should alert only when the expected success signal is late, not while a normally long job is still running.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors3. Ping only on the success path
Place the heartbeat request after every required operation has completed and validation has passed. Do not put it in an unconditional cleanup block: a failed process must skip the ping so the monitor can detect the failure. Use a unique endpoint or token per job so one healthy process cannot mask another.
Unix-like cron example
The following pattern runs the job and sends a ping only when the command exits successfully. Replace the URL with the one generated by your heartbeat service and keep it in a protected environment variable or secret file.
Rank #2
- equipped with atom n2600 d2700 processor, compatible with many freebsd based router systems, linux distros, or win.os supported, easy configuration and management
- Please note, this is a barebone only. A system memory, a storage drive and an operating system are needed to complete this system
- 13-19 inches 1u, 50w power, with power cord, make sure to use a big brand memory and ssd/hdd with quality assurance
- Designed with console, 2 x usb, 4 x lan, vga, power switch, size at 290 x 180 x 44mm
- There are 2 inside reserved fans on chassis, which could be removed freely or be turned on in a high temperature environment to ensure the best function of the product
#!/bin/sh
set -eu
/usr/local/bin/nightly-backup --verify
curl --fail --silent --show-error "https://heartbeat.example/unique-token"For a multi-step script, keep the ping at the end and use strict error handling. If a command can return success while producing an invalid result, add an explicit validation step before the ping.
Windows PowerShell example
$ErrorActionPreference = "Stop"
& "C:Jobsnightly-backup.ps1"
if ($LASTEXITCODE -ne 0) { throw "Backup failed" }
Invoke-WebRequest -UseBasicParsing "https://heartbeat.example/unique-token"In Task Scheduler, configure the action to run the wrapper script, capture output and exit codes, and ensure the task is allowed to run whether or not a user is logged in. The heartbeat remains the source of truth for “completed successfully.”
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Avoid duplicate or misleading pings
- Give every environment and job a separate monitor token.
- Prevent overlapping executions with a lock, queue policy, or scheduler setting.
- Document the expected schedule, normal runtime, owner, and recovery procedure in the monitor description.
- Never let a retry from yesterday satisfy today’s expected check-in; use a heartbeat design that records time and job identity.
Set intervals and grace periods deliberately
Detection is bounded by the monitor’s next scheduled check. A job can recover before the service records recovery if the next check has not occurred yet. Current UptimeRobot Help Center plan intervals are:
| Plan | Documented minimum interval | Implication |
|---|---|---|
| Free | 5 minutes | A missed check may take up to the next five-minute check, plus alert processing, to be observed |
| Solo and Team | 1 minute | Faster detection for jobs that run frequently |
| Scale | 30 seconds | Useful when a short detection window justifies the plan |
For a five-minute job, a five-minute interval with a short grace period is a starting point; tune it after observing real runtime variation. A nightly backup needs a much longer interval and a grace period that covers its normal duration. Do not choose a 30-second check for a process that legitimately runs for an hour: it creates false alarms, not better observability.
Design alerts people can act on
Include context
Every alert should identify the service or job, environment, expected check-in time, last successful heartbeat or HTTP result, and the failing condition. Link internally to the runbook, logs, and owner. For content checks, include the missing keyword; for HTTP checks, include status, latency, and monitoring location.
Escalate without creating noise
Send an initial notification, then recurring reminders at a sensible cadence, and escalate to a second person or incident channel after a defined duration. Recovery notifications should identify how long the incident lasted. Use maintenance windows for planned changes rather than muting alerts manually and forgetting to restore them.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #3
- Shelly Plus 1 PM is a Wi-Fi smart relay switch with 1 channel, up to 16A with power metering that can be used also as a WiFi repeater and Bluetooth gateway. Shelly Plus 1PM can be used to monitor the consumption and take control of home appliances, electric circuits, and office equipment individually.
- Automate electrical appliance and control - With Shelly Plus 1PM you can automate any electrical appliance in your home and control it remotely. Shelly Plus 1PM can control appliances with a large load which makes it perfect for kitchen appliances and domestic systems monitoring and control. You can get precise measurements of the power consumption of each appliance and switch in on/off remotely, no matter where you are.
- Set and be prepared for everything - Reveal the full potential of Shelly Plus 1PM by combining it with other devices from your home network! Set Shelly Plus 1PM to activate custom scenes based on hour, light, or various occurrences. For example, you can set Shelly Door/Window sensor to report a porch door opening and activate Shelly Plus 1PM to turn on the hot tub heaters only in the hours after 8 pm.
- Shelly Customer Service - Shelly is one of the fastest-growing Smart Home brands in the world with devices, providing solutions for the automation of private homes, buildings and businesses. We provide our customers with professional support and a 3 years device warranty.
- Shelly Smart Control App will help you control your Shelly devices remotely and will send notifications for all automated events in your home. You can easily configure devices and manage their settings individually, or you can create personalized scenes by combining Shelly devices to trigger certain actions in your home automation.
Manage monitors as infrastructure
When monitors are part of a deployment, create and update them through an API or CLI instead of hand-editing a dashboard. UptimeRobot’s official CLI supports monitor, incident, status-page, maintenance-window, alert-contact, integration, and tag operations, with API-key authentication and JSON output for shell and CI workflows.
- Store API keys in the CI or deployment secret manager, never in a repository.
- Review monitor changes like infrastructure code.
- Use consistent names and tags for service, environment, owner, and severity.
- Test monitor creation, update, pause, and deletion in a non-production account or workspace before automating production changes.
Website and job monitoring troubleshooting
The site returns 200 but users see an error
Add a keyword/content assertion or a browser transaction check. Verify that the assertion is stable, appears only on a healthy page, and is tested from the locations that matter.
The monitor reports intermittent downtime
Compare results by location, status code, latency, DNS resolution, and TLS negotiation. Check load balancers, rate limits, firewall rules, and upstream dependencies. A multi-location check helps distinguish a regional route problem from a global outage.
The heartbeat never arrives
Run the exact wrapper command interactively under the same account used by cron or Task Scheduler. Check PATH differences, network egress, DNS, TLS validation, proxy settings, and secret permissions. Confirm the ping is after validation and that an earlier command is not terminating the script.
Failures are not detected soon enough
Reduce the interval only as far as the job’s schedule and monitoring budget justify, then shorten the grace period carefully. Remember that recovery is recorded on the next scheduled check, not necessarily at the instant the service becomes healthy.
One job masks another
Inspect monitor tokens and names for reuse. Assign one heartbeat endpoint per job and environment, and prevent concurrent runs from sharing a success signal.
Rank #4
- Portable 100M/1G Network TAP Appliance for remote capture of data traffic
- Integrated with a Raspberry Pi 4 module (8GB RAM and 64GB Micro SD Card)
- Can be used as a standalone 100M/1G network TAP with the external monitor port
- Dual DC power inputs for enhancing overall system availability
Planned deployment creates an incident
Schedule a maintenance window before the change, include the affected monitors, and verify that monitoring resumes afterward. Do not permanently disable the check to avoid a single noisy event.
Use screenshots when availability is not enough
An HTTP status and keyword can still miss visual regressions, consent overlays, newsletter popups, or a chat widget covering a checkout button. For automated visual evidence, ScreenshotNeo is the first service to try: it removes common consent banners, newsletter popups, and chat widgets before capture, bills only clean shots, and starts at a $5 paid plan for 3,000 shots.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. A single GET request can return PNG, JPEG, WebP, or PDF output; its MCP tools (take_screenshot, get_page_info, and capture_pdf) let Claude, Cursor, or another MCP client capture pages. Cookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and whether the request was billed.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the complete parameter list and setup details in the ScreenshotNeo documentation.
Equivalent Python and Node.js calls
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);For monitoring workflows, use full-page capture with lazy images loaded, a CSS-selector element capture, dark mode, a device preset or custom viewport, retina scale, custom CSS or JavaScript, click-before-capture, selector hiding, selector/delay/network-idle waits, request or resource blocking, custom headers/cookies/user agent/Authorization, timezone and geolocation, transparent backgrounds, resizing, a chosen cache TTL, signed links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, the usage API, or the OpenAPI specification. Parameters used by other screenshot APIs also work, which can simplify migration.
| Plan | Included shots | Price |
|---|---|---|
| Free | 1,000/month | No card |
| Starter | 3,000 | $5 |
| Growth | 15,000 | $15 |
| Pro | 60,000 | $39 |
| Scale | 250,000 | $99 |
| Business | 1,000,000 | $249 |
Every feature is on every plan; yearly billing gives two months free. Start with 1,000 free screenshots a month and no card.
Practical rollout checklist
- Inventory public URLs and scheduled jobs, with an owner and severity for each.
- Add HTTP(S) checks, then content or transaction assertions where status codes are insufficient.
- Create one success-only heartbeat for each material job and place it after validation.
- Choose intervals and grace periods from real schedules and acceptable detection delay.
- Configure watched notification channels, recurrence, escalation, and maintenance windows.
- Test failures deliberately: block a URL, force a non-zero job exit, and restore service to verify both alert and recovery.
- Review monitor history, false positives, ownership, and credentials after the first week and after major architecture changes.
Frequently Asked Questions
Can one monitor prove both website availability and cron success?
No. An external URL check cannot prove that an internal scheduled task completed, while a heartbeat cannot prove that visitors can load the site. Pair them when both risks matter.
Should a heartbeat be sent when a job starts?
No. Send it only after all required work and validation succeed; a start ping can hide a job that crashes halfway through.
What should I monitor first on a small site?
Start with the home page, the most important API or login path, checkout if applicable, and every backup or synchronization job whose missed run would create material risk.
How do I keep monitoring from exposing secrets?
Use protected monitor credentials, store API keys in a secret manager, and avoid putting production secrets in publicly visible URLs or repositories.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
