Monitor Types Explained
Statly supports several monitor types for different use cases.
HTTP/HTTPS Monitor
The most common type. Sends an HTTP request and checks:
- Response status code matches expected (e.g., 200)
- Response time is within threshold
- Optional: Response body contains expected text
Best for: Websites, APIs, webhooks
TCP Monitor
Opens a TCP connection to verify a port is accessible.
Best for: Databases, mail servers, custom services
DNS Monitor
Queries DNS servers to verify records resolve correctly.
- Check A, AAAA, CNAME, MX, TXT records
- Verify record values match expected
Best for: Ensuring DNS propagation, monitoring DNS health
WebSocket Monitor
Establishes a WebSocket connection and optionally sends/receives messages.
Best for: Real-time applications, chat services, live data feeds
Error Rate Monitor
Integrates with Statly Observe to monitor error rates from your application.
Best for: Application health, exception monitoring