Host Monitoring

Central Logging can track the health of your servers. The CL Agent periodically sends system information to Central Logging, and you get alerted if a host stops checking in.

How It Works

When the CL Agent runs on a server, it sends periodic check-ins to Central Logging with system information. Central Logging tracks when each host was last seen and alerts you if a host goes missing.

Host Information

Each host check-in reports:

• Hostname — The system hostname
• OS Version — Operating system version
• Kernel Version — Kernel version
• Architecture — CPU architecture (e.g. amd64, arm)
• External IP — The host’s external IP address
• Uptime — System uptime
• CL Agent Version — The version of the CL Agent running on the host

Missing Host Detection

Each host has a Max Check-in Duration setting (default: 30 minutes). If a host has not checked in within this duration, it is considered missing in action (MIA) and an alert is sent through your configured notification channels.

You can adjust the max check-in duration per host from the host detail page. Setting it to 0 disables MIA detection for that host.

Hosts can also be marked as inactive to disable monitoring for hosts that have been intentionally decommissioned.

Process Monitoring

Central Logging can also collect and display the running processes from your hosts. View the process list from the host detail page with sortable columns.

Host API

If you want to send host information from a custom agent, send a POST request to:

POST /api/v1/host

With a JSON body containing at minimum a host_id field:

{
    "host_id": "unique-host-identifier",
    "hostname": "web-server-1",
    "os_version": "Ubuntu 22.04",
    "kernel_version": "5.15.0",
    "architecture": "amd64",
    "external_ip": "203.0.113.1",
    "uptime": 86400
}