Monitors Overview
Monitors are the core unit of PingSLA. Each monitor represents a target you want to continuously check for availability and performance.
Monitor Types
| Type | Protocol | Use Case |
|---|---|---|
| HTTP(S) | HTTP/HTTPS | Web APIs, websites, health endpoints |
| Ping | ICMP | Servers, VMs, network appliances |
| Keyword | HTTP/HTTPS | Detect specific strings in page content |
| SSL | TLS handshake | Certificate expiry and chain validity |
How Checks Work
Probe Worker (Region A) ──┐
Probe Worker (Region B) ──┼──→ Your Endpoint → Response → Evaluate → Record
Probe Worker (Region C) ──┘
- Probe workers independently check your endpoint on the configured interval
- Each check records: status code, response time, and probe region
- Results are aggregated at the API server
- Alert policies evaluate aggregated results to determine incident creation
Check Intervals
| Interval | Plans |
|---|---|
| 30 seconds | Business, Enterprise |
| 60 seconds | All plans |
| 5 minutes | All plans |
| 10 minutes | All plans |
| 30 minutes | All plans |
30-second intervals consume more monitoring quota. See Usage & Limits →
Monitor States
| State | Meaning |
|---|---|
UP | All probes reporting success |
DOWN | Failure threshold exceeded |
DEGRADED | Partial probe failures (some regions failing) |
PAUSED | Manually paused — checks are suspended |
PENDING | First check not yet completed |
Failure Thresholds
A monitor only transitions to DOWN after the configured number of consecutive failures. This prevents false positives from transient network blips.
Default: 2 consecutive failures before DOWN state.
Default: 1 success to recover to UP state.
Both values are configurable per alert policy.
Probe Locations
PingSLA operates probe workers in the following regions:
| Region | Location |
|---|---|
us-east-1 | N. Virginia, USA |
eu-west-1 | Dublin, Ireland |
ap-southeast-1 | Singapore |
me-south-1 | Dubai, UAE |
You can configure monitors to check from all regions or a specific subset.
Response Time Tracking
Each check records the full response time (DNS + TLS + TTFB + transfer). These are displayed in:
- Monitor detail graphs (30-day history)
- Incident timeline
- SLA reports
SLA Calculation
SLA % = (Uptime Minutes / Total Minutes) × 100
Downtime is measured from incident creation to incident resolution. Maintenance windows (if configured) are excluded from SLA calculations.