Getting Started
Get up and running with izli.io in under 5 minutes. Create your first monitor and start monitoring your applications.
Getting Started
Welcome to izli.io! This guide will help you set up your first monitor and understand the basics of synthetic monitoring.
Quick Start
Create an Account
Sign up at izli.io/signup. You can start with our free Hobby plan which includes:
- 10 uptime monitors
- 3,000 browser runs/month
- 25,000 API runs/month
Create Your First Monitor
After signing in, you'll be guided through creating your first monitor. Choose from:
- URL Monitor - Simple HTTP/HTTPS availability check
- Browser Journey - Multi-step user flow testing
- API Monitor - REST API testing with assertions
Configure Alerts
Set up notifications so you know when things break:
- Go to Settings and add a Slack, Email, or Webhook channel
- Create an alert rule for your monitor
Monitor Your Results
View your dashboard to see:
- Current status of all monitors
- Recent run history
- Performance trends
- Active incidents
Core Concepts
Understanding these concepts will help you get the most out of izli.io.
Monitors
Monitors are the core unit of izli.io. Each monitor performs a specific check on a schedule:
| Type | Use Case | Example |
|---|---|---|
| URL | Simple uptime checks | Check if https://api.example.com/health returns 200 |
| API | Multi-step API workflows | Authenticate, then fetch user data |
| TCP | Port connectivity | Verify database port 5432 is accessible |
| DNS | DNS record validation | Ensure MX records are correctly configured |
| Heartbeat | Cron job monitoring | Verify daily backup job completes |
| Journey | User flow testing | Test login → dashboard → logout flow |
Runs
A run is a single execution of a monitor. Each run captures:
- Status -
passed,failed,running, orpending_retry - Duration - How long the check took
- Assertions - Which checks passed or failed
- Artifacts - Screenshots, traces, and logs (for journeys)
Agents
Agents execute your monitors from different geographic locations. izli.io provides managed agents in multiple regions:
- Global (auto-selected)
- US East
- US West
- EU West
- EU Central
- Asia Pacific South
- Asia Pacific Northeast
Alert Rules
Alert rules define when and how you get notified:
- Consecutive Failures - Alert after N failed runs
- Error Rate - Alert when error rate exceeds threshold
- Latency Threshold - Alert when response time exceeds threshold
- Visual Diff - Alert when UI changes unexpectedly (journeys only)