Start with the failure you want to hear about. Statusfield can follow a vendor's reported incidents, check your own website or API, and watch for missing check-ins from scheduled jobs. Choose a monitor, configure its rules, then test your alert destination.
Which monitor do I need?
| What you need to know | Choose | What you configure |
|---|---|---|
| Is a third-party service reporting an outage? | Vendor monitoring | The service, supported components or regions, and status changes you want to hear about |
| Is my website or API returning the right response? | Uptime monitoring | A public HTTPS URL, response rules, check locations and frequency |
| Did my cron job, backup or sync finish its work? | Heartbeat monitoring | A check-in after successful work, an expected interval and a grace period |
These answer different questions. A green vendor status page can coexist with a failing website. A working website does not tell you whether last night's backup finished. Add the monitors that match your responsibilities; you do not need every type to get started.
Heartbeat availability follows the current access terms. For renewal reminders, use separate SSL certificate and domain expiry monitors.
Create your account and activate monitoring
- Create an account using an available sign-in method. If you use email, follow the verification link in your inbox.
- Choose the monitor types offered in setup, or choose Set up monitors later to continue to trial review. If you started from a vendor's alert form, check that the saved service is selected.
- Configure each selected monitor type before trial review. Choose vendor components, enter your website or API settings, and set a heartbeat interval where access is available. For vendors, you can also review available incident history; an empty preview does not prove the vendor has never had an outage.
- On Confirm & activate, review your selected plan, its trial terms, and its price after the trial.
- Before activating, use Send test alert and check the inbox shown beside it. The message is labeled as a test. If sending fails, use Try sending again; check spam if a sent message is missing.
- Activate the trial if eligible. Returning customers use their existing plan or choose a paid subscription. Successful setup opens Monitors with the monitors you configured. If you chose Set up monitors later, add your first monitor there. For a new heartbeat, open its Settings to get the check-in URL and send the first signal.
A saved monitor is only the start
Entering your email on a vendor page saves a pending choice. Verify your address and complete setup. The pending verification window is separate from the full trial; it does not provide a permanent free alerting plan. Continued monitoring after a trial requires a paid subscription.
See current plans and trial terms. You can manage your subscription and cancellation from billing settings.
Verify delivery after setup
To send another test after activation, open Integrations, find the destination, and use its test action. Check the actual inbox or channel: a successful request alone does not establish that everyone can see the message. An email test does not also verify Slack or Teams.
Receiving the test confirms that destination worked at the time of the test. Also check your monitor's notification rules: a destination test does not prove that a real failure will match those rules.
Choose relevant components and notifications
- Open a service from Monitors to reach its Overview. Under Monitored components, choose Add or remove (or Pick components for an empty selection).
- Choose Only the components I choose, select the components or regions your team uses from the options that provider exposes, then click Save.
- Open Notifications and configure each monitor's destinations and status filters.
- Verify each destination with a test. Recovery notifications follow the configured alert rules.
Vendor checks follow reported status changes. Update timing depends on the provider, polling, and delivery; a green vendor page does not rule out an account-specific issue.
Monitor your own website or API
An uptime monitor checks your URL directly, independently of the hosting provider's status report.
- Open Create uptime monitor in your workspace. Give it a recognizable name, such as Production API, and enter a public HTTPS URL.
- Open Advanced settings. Choose the expected status code or range, the response-time threshold for degradation, and the timeout. Add text or JSON response-body checks when a successful status code alone is not enough.
- Select check locations and frequency. Each location uses one monitor unit; available choices depend on your plan.
- Use Test now to inspect a response with your settings. This test runs from the app server; scheduled checks use your selected locations.
- Choose notification destinations for degraded, outage and recovery events, then create the monitor. Review its recorded checks after creation.
For example, a health endpoint might need to return HTTP 200 and an expected JSON value. A valid but slow response can be degraded; an unexpected status, failed body rule or timeout is an outage. A successful HTTP check does not run a browser through a login or checkout.
Monitor a cron job, backup or sync
A heartbeat monitor waits for your job to contact Statusfield. It can notice a missing check-in even when the job never runs and cannot send its own error alert.
- If heartbeat access is available in your workspace, open Create heartbeat monitor. Name the job, set its expected interval and allow a grace period for runs that finish late.
- Choose destinations for missing check-ins or reported failures and for recovery. Create the monitor to get its private check-in URL.
- Add that URL to the job after the work and your success checks finish. Keep the URL private; it contains the monitor's token.
- Send the first successful check-in and confirm it appears in the monitor. Missing-check-in monitoring starts after the first signal, not merely when you create the monitor.
- For a known job failure, call the same URL with
/failappended. Statusfield processes that failure without waiting for the expected interval and grace period to pass.
For a five-minute sync with one minute of grace, a check-in at 12:00 sets the next expected check-in at 12:05. If it is still missing after 12:06, the missed deadline can open an incident. Deadlines are evaluated every minute; alert delivery also takes processing time.
For a backup, check the backup command's result before sending success. Perform restore checks separately: a received ping does not establish that the archive is usable. See backup, inventory sync and report export examples.
Use a disposable test job to check the first signal, a missed deadline and recovery. Keep your production job running. The grace period tolerates lateness; it is not a maintenance calendar or a record of every expected run.
Watch the process that does your monitoring
If your own scheduler or health-check process fails, its silence can look like everything is fine. Have that process send a heartbeat after it completes its checks. Statusfield can then watch for a missed signal outside that process. Choose an alert destination that remains available when your monitored system fails, and test it.
For engineering teams
Start with a recurring responsibility: your production API, a nightly backup, or a dependency such as GitHub Actions. GitHub's vendor status describes the Actions service; a heartbeat from your own job describes whether that job checked in. Route each monitor's relevant updates to the people who can investigate.
For internal IT teams
Start with the business tools staff ask about. Route alerts to IT and create a board containing the monitors staff need to see. Share its link in your intranet or incident update.
Unprotected boards are viewable by anyone with the link and do not grant workspace access. Include only services and labels you intend to share. Board features and limits depend on the plan. Adding an internal service means your team maintains its status manually.
If setup stops
- No verification email: check spam, then use the resend control when available. If a link expired, request a fresh link rather than repeatedly opening it.
- No trial available: trials are limited to eligible first-time customers. Check your existing subscription or choose a paid plan.
- Activation failed: read the message and retry using the activation control. A saved service selection alone does not mean alerts are active.
- Channel needs approval: ask your workspace administrator for the required installation permission, or use an available destination your team controls.
- Test arrives but no incident alerts: check that monitoring and the destination are active, the plan includes the channel, and notification rules include the relevant components and severity. There may have been no matching status change.
Choose a plan by workflow
Compare alert channels, sharing and reporting first, then confirm monitor and member capacity. Current limits and prices are listed below.
- Basic: $5/mo - 5 monitors
- Starter: $20/mo - 20 monitors
- Pro: $60/mo - 40 monitors
- Team: $150/mo - 90 monitors