Monitor Types
Overview of different monitoring types available in StatusPageOne
Monitor Types
StatusPageOne specializes in HTTP/HTTPS monitoring to ensure your web services, APIs, and websites are always available and performing correctly.
Available Monitor Types
Currently, StatusPageOne focuses on comprehensive HTTP/HTTPS monitoring with two distinct check types:
🔍 Uptime Monitoring
Monitors whether your service is responding with successful HTTP status codes.
Perfect for:
- • Website availability monitoring
- • API health endpoints
- • Service uptime verification
- • Load balancer health checks
Learn More →
📄 Content Monitoring
Checks for the presence or absence of specific content in HTTP responses.
Perfect for:
- • Content delivery verification
- • Error page detection
- • Dynamic content validation
- • API response verification
Learn More →
Why HTTP/HTTPS Only?
StatusPageOne focuses exclusively on HTTP/HTTPS monitoring because:
Web-First Approach
Most modern services expose HTTP endpoints for health checking, making HTTP monitoring the most versatile and widely applicable approach.
Rich Validation Options
HTTP monitoring allows for complex validation including response codes, content matching, headers, authentication, and response times.
Comprehensive Metrics
HTTP requests provide detailed performance metrics including response times, SSL certificate status, and detailed error information.
Application-Level Monitoring
Unlike ping or port monitoring, HTTP checks validate that your application is actually working, not just that the server is responding.
Supported Protocols
- HTTPS (recommended): Secure HTTP with SSL/TLS certificate validation
- HTTP: Standard HTTP for internal services or development environments
HTTP Methods Supported
Most common, default method
For API endpoints requiring POST
For REST API monitoring
For partial update endpoints
Advanced Features
All monitor types in StatusPageOne include:
Authentication Support
- Basic Authentication: Username and password
- Custom Headers: For API keys, tokens, and custom authentication schemes
Request Customization
- Custom Headers: Add any HTTP headers your service requires
- Timeout Configuration: 5-60 second request timeouts
- Redirect Handling: Option to follow or ignore HTTP redirects
Validation Options
- Response Code Validation: Specify expected HTTP status codes
- Content Matching: Search for specific text in responses
- SSL Certificate Monitoring: Automatic SSL certificate validation for HTTPS endpoints
Performance Monitoring
- Response Time Tracking: Monitor how quickly your services respond
- Multi-Region Checks: Validate performance from multiple geographic locations
- Retry Logic: Configurable retry attempts (0-3) to reduce false positives
Choosing the Right Monitor Type
🎯 Decision Guide
Choose Uptime Monitoring when:
- • You want to monitor if a service is responding
- • You have dedicated health check endpoints
- • You care primarily about service availability
- • Your service returns consistent status codes
Choose Content Monitoring when:
- • You need to verify specific content is present
- • You want to detect error pages that return 200 status
- • You need to monitor dynamic content changes
- • You want to validate API response content
Next Steps
Ready to set up monitoring? Check out these guides:
- HTTP/HTTPS Monitoring Details - Deep dive into HTTP monitoring configuration
- Create Your First Monitor - Step-by-step monitor creation guide
- Configure Alerting - Set up notifications for monitoring events
Future Monitor Types
We're constantly evaluating additional monitoring capabilities based on user feedback:
- TCP Port Monitoring: For non-HTTP services
- Ping/ICMP Monitoring: For network connectivity checks
- DNS Monitoring: For DNS resolution validation
- Certificate Monitoring: Dedicated SSL certificate expiration alerts
Have a specific monitoring need? Let us know - your feedback helps shape our roadmap.
Improve this page
Found an error or want to contribute? Edit this page on GitHub.