Getting Started
This guide walks through the common flow for creating a monitor, reviewing results, and connecting it to the rest of Testable Monitoring.
1. Choose a Monitor Type
- HTTP - Websites and APIs.
- Ping - Host reachability.
- Port Monitor - TCP service availability.
- Heartbeat - Services and jobs that send pings to Testable.
- Custom - Browser journeys, API collections, and scripted scenarios.
2. Configure the Target
Enter the target details for the selected type: URL and method for HTTP, host for ping, host and port for port monitors, heartbeat timing for heartbeat monitors, or a scenario for custom monitors.
3. Organize the Monitor
Select or create a folder and group, give the monitor a clear name, and optionally add a Markdown description and tags. These fields drive navigation, filtering, status page associations, and maintenance window inheritance.
4. Set Failure Rules
For runner-based monitors, choose how many consecutive failures create an incident and how many consecutive successes resolve it. Add confirmation checks when you want failures retried immediately on another runner when possible.
5. Configure Schedules or Heartbeat Timing
HTTP, ping, port, and custom monitors run on schedules from selected regions. Heartbeat monitors expect your service to send POST requests at the configured frequency with an acceptable delay.
6. Add Optional Features
- Associate maintenance windows.
- Use default or custom notifications.
- Override success criteria and metrics.
- Add tags for filtering and broad associations.
7. Review Results
Open the monitor detail page to see current status, uptime stats, metrics, incidents, activity, checks or pings, and comments. Incident pages provide type-specific diagnostics when something fails.