Service Monitoring¶

Monitor the health and performance of your web services, applications, and infrastructure.

Overview¶

Komandorr's service monitoring provides real-time health checks with customizable intervals, service grouping, and detailed performance metrics.

Adding Services¶

Via Web Interface¶

Navigate to the Services page
Click Add Service
Configure the service:

Name: Production API
URL: https://api.example.com
Type: API
Group: Production
Check Interval: 60 seconds
Enabled: Yes

Click Save

Via API¶

curl -X POST http://localhost:3000/api/services \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Production API",
    "url": "https://api.example.com",
    "type": "app",
    "group": "Production",
    "interval": 60,
    "enabled": true
  }'

Service Types¶

Komandorr supports different service types:

Type	Icon	Description
Website		Public websites and web applications
App		Internal applications and services
Panel		Admin panels and dashboards
Server		Server endpoints and APIs

Service Groups¶

Organize services into logical groups:

Production - Live production services
Staging - Pre-production testing environment
Development - Development environment
Infrastructure - Core infrastructure components

Creating Groups¶

Groups are created automatically when you assign a service to a group name.

Monitoring Metrics¶

For each service, Komandorr tracks:

Status¶

Up - Service is responding (HTTP 200-299)
Down - Service is not responding or error
Unknown - No data available yet

Response Time¶

Current response time in milliseconds
Historical response time graph (last 100 points)
Average, min, and max response times

Uptime¶

Uptime percentage calculation
Last checked timestamp
Total checks performed

Check Intervals¶

Configure how often each service is checked:

Minimum: 30 seconds
Default: 60 seconds
Maximum: 3600 seconds (1 hour)

Performance

Higher check intervals reduce server load but provide less granular monitoring.

Service Actions¶

Edit Service¶

Update service configuration at any time through the web interface.

Delete Service¶

Remove a service and all its historical data.

Disable/Enable¶

Temporarily disable monitoring without deleting the service.

Check Now¶

Manually trigger an immediate health check.

Advanced Features¶

Custom Headers¶

Add custom HTTP headers to health check requests (coming soon).

Expected Status Codes¶

Configure which HTTP status codes indicate success (coming soon).

Timeout Configuration¶

Set custom timeout values per service (coming soon).

Best Practices¶

Group Logically: Organize services by environment or function
Appropriate Intervals: Balance monitoring frequency with resource usage
Descriptive Names: Use clear, descriptive names for easy identification
Regular Reviews: Periodically review and clean up unused services