Overview

What is Site Tracker?

Each site tracker is linked to a single normalized URL. The tracker combines the result of the external frontend probe and the WordPress heartbeat probe, if available, to store the final state of the site.

If the plugin is not connected, the decision is made only with the frontend probe. If the plugin is connected, the heartbeat result is processed in the same loop and the final status is saved as a single status value.

Control Loop

1. 1

   Scheduler queues appropriate sites

   Verified sites are added to the control queue in order according to the schedule interval.
2. 2

   Frontend probe works

   Anchor Uptime sends an external HTTP request to the URL and measures the status code and response time.
3. 3

   Heartbeat probe works if there is active plugin token

   The panel calls the /wp-json/anchoruptime/v1/heartbeat endpoint opened on WordPress.
4. 4

   Decision engine calculates the combined state

   The frontend and heartbeat signals are combined to produce a single status decision and description.
5. 5

   Incident management is implemented

   If your site is down, the incident will be opened immediately; gradual notifications will be sent as long as the incident remains open.

State Logic

The current decision engine generates a degraded value instead of warn. In the dashboard, maintenance is a separate parent status; it overlays the normal site status.

Next Steps