Monitoring Capabilities¶

Overview¶

UptimeHunt provides comprehensive monitoring capabilities designed to ensure your services remain available and perform optimally. This guide explores the monitoring features, methodologies, and capabilities of the platform.

Supported Monitoring Types¶

HTTP/HTTPS Monitoring¶

Comprehensive web and API endpoint monitoring.

Protocol Support:

HTTP (unencrypted)
HTTPS (encrypted with SSL/TLS)

Capabilities:

Multiple HTTP methods (GET, POST, HEAD)
Request customization
Authentication support
Header configuration
Response validation

Metrics Collected:

Response status codes
Response times
Content availability
SSL certificate validation
Connection metrics

Learn more about HTTP Monitoring →

ICMP PING Monitoring¶

Network connectivity and latency monitoring.

Protocol:

ICMP (Internet Control Message Protocol)

Capabilities:

IPv4 and IPv6 support
Domain name resolution
Latency measurement
Packet loss detection

Metrics Collected:

Round-trip time (min/avg/max)
Packet loss percentage
Host reachability
Network latency

Learn more about PING Monitoring →

Monitoring Methodology¶

Check Execution¶

Scheduling:

Checks executed at configured intervals
Range: 1-60 minutes per service
Distributed across global probe network
Consistent timing maintained

Process:

Check scheduled based on interval
Probe selected from global network
Check executed (HTTP request or PING)
Results collected and processed
Metrics calculated and stored
Status updated on dashboard

Check Intervals¶

Interval Selection:

Select check frequency based on service criticality:

High Frequency (1-3 minutes):

Critical production services
Revenue-generating applications
Customer-facing systems
SLA-bound services

Medium Frequency (5-10 minutes):

Important but non-critical services
Internal applications
Development/staging environments
Standard monitoring needs

Low Frequency (15-60 minutes):

Low-priority services
Scheduled task verification
Resource-constrained monitoring
Cost optimization scenarios

Considerations:

Higher frequency = faster detection
Balance between coverage and resources
Consider target system impact
Factor in alert fatigue

Global Probe Network¶

Multi-Location Monitoring¶

Checks performed from multiple geographic locations:

Benefits:

Detect regional outages
Identify routing issues
Validate global accessibility
Monitor CDN performance
Reduce false positives

Coverage:

Multiple continents
Diverse ISPs and networks
Geographic distribution
Redundant checking

Learn more about Global Probes →

Monitoring Features¶

Status Determination¶

Service Status:

Services marked as Up or Down based on check results.

HTTP Services:

Up Status When:

HTTP response received
Status code indicates success (2xx, 3xx)
Response within timeout period
No connection errors

Down Status When:

Connection refused or timeout
HTTP error status (4xx, 5xx)
SSL/TLS certificate errors
Response exceeds timeout

PING Services:

Up Status When:

ICMP echo reply received
Packet loss below threshold
Response time within limits

Down Status When:

100% packet loss
Host unreachable
No response within timeout

Response Time Measurement¶

HTTP Monitoring:

Measures complete request cycle:

DNS resolution
TCP connection establishment
SSL/TLS handshake (HTTPS)
HTTP request transmission
HTTP response reception
Complete data transfer

Reported as:

Total response time in seconds
Precision to milliseconds

PING Monitoring:

Measures network round-trip:

ICMP echo request transmission
Network propagation time
Target processing time
ICMP echo reply return
Total round-trip time

Reported as:

Minimum, average, maximum RTT
Precision to milliseconds
Packet loss percentage

Historical Data¶

Data Collection:

All checks stored
Complete check history
Metrics and status preserved
Long-term trend data

Available Metrics:

Check timestamps
Success/failure status
Response times
Error messages
Probe locations

Analysis Capabilities:

Trend identification
Performance patterns
Availability calculations
Incident correlation

Monitoring Best Practices¶

Service Selection¶

What to Monitor:

Public-facing websites
Critical APIs
Authentication services
Payment processors
Database connectivity
Infrastructure components
Third-party dependencies

What to Avoid:

Rate-limited endpoints
Non-production test systems (unless needed)
Extremely resource-intensive checks
Services with automatic blocking mechanisms

Configuration Strategies¶

Layered Monitoring:

Implement multiple monitoring layers:

Infrastructure Layer:

PING monitoring for servers
Network device availability
Connectivity verification

Application Layer:

HTTP monitoring for services
API health endpoints
Application functionality

End-User Experience:

Full page load monitoring
User workflow simulation
Geographic performance

Interval Optimization¶

Balance Factors:

Detection speed requirements
Resource constraints
Cost considerations
Alert fatigue prevention

Recommendations:

Critical services:

Type: HTTP
Interval: 1-3 minutes
Reasoning: Rapid detection essential

Standard services:

Type: HTTP/PING
Interval: 5 minutes
Reasoning: Balance of coverage and efficiency

Supplementary checks:

Type: PING
Interval: 10-30 minutes
Reasoning: Basic availability verification

Monitoring Metrics¶

Availability Metrics¶

Uptime Percentage:

Uptime % = (Successful Checks / Total Checks) × 100

Industry Standards:

99.99% (Four Nines): 52.56 minutes downtime/year
99.9% (Three Nines): 8.76 hours downtime/year
99% (Two Nines): 3.65 days downtime/year
95%: 18.25 days downtime/year

Downtime Calculation:

Downtime = Total Checks - Successful Checks
Downtime Duration = Downtime Count × Check Interval

Performance Metrics¶

Response Time Statistics:

Minimum response time
Average response time
Maximum response time
Percentile calculations (planned)

Performance Baselines:

Establish normal operating ranges:

Fast: <100ms
Acceptable: 100-500ms
Slow: 500-2000ms
Critical: >2000ms

Error Metrics¶

Error Categories:

Connection errors
Timeout errors
HTTP status errors
SSL/TLS errors
DNS resolution errors

Error Rate:

Error Rate = (Failed Checks / Total Checks) × 100

Advanced Capabilities¶

Planned Features¶

Future monitoring enhancements:

Enhanced HTTP Monitoring:

Custom response validation
Content matching
Header validation
Response size limits
Follow redirects configuration

Advanced PING Options:

Packet size configuration
Packet count customization
Timeout adjustment
DSCP/QoS marking

Additional Protocols:

TCP port monitoring
UDP monitoring
DNS resolution checking
SSL certificate expiration monitoring

Smart Alerting:

Alert threshold configuration
Escalation policies
Alert grouping
Notification channels

Monitoring Limitations¶

Current Limitations¶

Protocol Support:

Limited to HTTP/HTTPS and ICMP
No custom protocol monitoring
No application-specific protocols

Check Customization:

Fixed timeout values
Limited response validation
No custom scripting

Concurrency:

Checks executed sequentially
No parallel request testing
No load testing capabilities

Platform Constraints¶

Check Frequency:

Minimum interval: 1 minute
Maximum interval: 60 minutes
No sub-minute checking

Data Retention:

Current: Unlimited retention
Future: May implement retention policies

Integration with Other Features¶

Projects¶

Organize monitoring services:

Group related services
Logical categorization
Visual organization

Learn more about Projects →

Alerts (Planned)¶

Automated notifications:

Service down alerts
Performance degradation
Recovery notifications

Learn more about Integrations →

API Access¶

Programmatic monitoring management:

Create/edit services via API
Retrieve check results
Access metrics programmatically

Learn more about API →