Monitoring
Monitoring overview
Choose Website, API, or Heartbeat monitoring for the service or process you need to watch.
Choose the type of monitor that matches what you need PingAgain to watch.
Choose a monitor
| Monitor | Use it for | What it tells you |
|---|---|---|
| Website | A public website or customer-facing web application | Uptime, certificate, DNS, domain-registration, sitemap, broken-link, and mixed-content results |
| API | A public HTTP API or endpoint | Whether the configured request succeeds and its response matches your rules |
| Heartbeat | A scheduled job, backup, sync, or background task | Whether the expected signal arrived on time |
A Website is the right choice for complete website monitoring. Use an API monitor when you need to check an HTTP endpoint, request method, headers, or response rules. Use a Heartbeat when a scheduled job or process should contact PingAgain after it finishes.
Read the result
Every result includes a state and observation time. One Website check can be healthy while another is still Checking, Partial, or temporarily unavailable because the checks contact different services and run on different schedules.
Open the monitor before acting on its summary. The detail page explains what PingAgain found and whether more information is still expected.
Next: add a Website, configure API monitoring, or create a Heartbeat.