Core Concepts
Monitors
Learn about API, Ping, TCP, DNS, and SSL monitors for tracking service health
Monitors are the core of Kener. They continuously check the health of your services and track their availability.
Monitor Types
Kener supports multiple monitor types for different use cases:
API Monitor
Check HTTP/HTTPS endpoints for availability and response codes.
{
"type": "API",
"url": "https://api.example.com/health",
"method": "GET",
"expectedStatusCode": 200,
"timeout": 10000
}
Options:
url- The endpoint to checkmethod- HTTP method (GET, POST, PUT, etc.)expectedStatusCode- Expected response codeheaders- Custom headers to sendbody- Request body for POST/PUT requests
Ping Monitor
Simple ICMP ping to verify server availability.
{
"type": "PING",
"host": "server.example.com"
}
TCP Monitor
Check if a specific port is open and responding.
{
"type": "TCP",
"host": "server.example.com",
"port": 443
}
DNS Monitor
Verify DNS records are resolving correctly.
{
"type": "DNS",
"host": "example.com",
"recordType": "A"
}
SSL Monitor
Track SSL certificate expiration and validity.
{
"type": "SSL",
"host": "example.com",
"port": 443
}
Creating a Monitor
Via Admin Panel
- Navigate to
/manage/monitors - Click "Add Monitor"
- Fill in the monitor details
- Save and activate
Via API
curl -X POST https://your-kener.com/api/monitors \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "API Health Check",
"type": "API",
"url": "https://api.example.com/health",
"interval": 60
}'
Monitor Status
Monitors can have the following statuses:
| Status | Description |
|---|---|
| UP | Service is operational |
| DOWN | Service is not responding |
| DEGRADED | Service is slow or partially working |
| MAINTENANCE | Scheduled maintenance in progress |
Check Intervals
Configure how often monitors run:
- 1 minute - Critical services
- 5 minutes - Standard monitoring
- 15 minutes - Less critical services
Alerting
Set up alerts for monitor status changes:
- Go to monitor settings
- Configure alert thresholds
- Add notification channels
- Save settings
Best Practices
- Start simple - Begin with basic health endpoints
- Use appropriate intervals - Don't over-monitor
- Set meaningful names - Make them descriptive
- Group related monitors - Organize by service
- Test your alerts - Verify notifications work