Monitoring
HTTP/HTTPS Monitors
Monitors automatically check your services at regular intervals and update component statuses when failures are detected.
How Monitors Work
PingBase sends HTTP/HTTPS requests to your service endpoints at configurable intervals. Each check records the response status code, response time, and SSL certificate validity. If a check fails (unexpected status code, timeout, or connection error), it counts toward the failure threshold.
Monitors run on distributed workers to ensure reliability. A single failed check does not trigger an incident — the failure threshold must be exceeded first.
Monitor Types
| Type | Description |
|---|---|
| HTTP | Sends an HTTP request and checks the response status code. |
| HTTPS | Same as HTTP but also validates the SSL certificate. |
| PING | Sends ICMP ping packets to check host reachability. |
| TCP | Attempts a TCP connection to a specific host and port. |
| DNS | Performs a DNS lookup and validates the response. |
| Keyword | Checks if the response body contains (or doesn't contain) a specific keyword. |
Configuration Options
Auto-Incident Creation
When consecutive failures exceed the Failure Threshold, PingBase automatically:
- 1Creates an incident with status "Investigating" and impact "Minor"
- 2Updates the linked component status to "Major Outage"
- 3Sends notifications to all subscribers
- 4When the monitor recovers, automatically resolves the incident
Response Time Tracking
Every monitor check records the response time in milliseconds. This data is available in Dashboard → Analytics where you can view response time trends, p50/p95/p99 percentiles, and identify performance degradation over time.