Health Monitoring

Health Monitoring gives operations and platform teams continuous visibility into server CPU, memory, disk, disk I/O, and agent status so they can catch resource bottlenecks before they become outages.

When To Use It

Use Health Monitoring when a server, virtual machine, or supported host needs resource-level monitoring.
Use Endpoint Monitoring when the user-facing risk is whether a URL or application endpoint responds successfully.
Use Windows Event Monitoring when the risk is a Windows event log, event ID, event source, or severity pattern.
Use SSL, DNS, and Domain Monitoring when the risk is certificate expiration, DNS behavior, or domain status rather than host-resource pressure.

Supported Systems

Health Monitoring supports Linux distributions, Windows Server versions, and macOS CLI workflows for teams that need server and host visibility across common operating systems.

System	Support
Linux	Ubuntu 18.04+, CentOS 7+, and Debian 10+.
Windows Server	Windows Server 2016, 2019, and 2022.
macOS	macOS 10.15 Catalina and later for CLI-only support.

Prerequisites

A Bitaic account with permission to install agents, configure hosts, and manage alert thresholds.
A supported server or host where the Health Monitoring agent can be installed.
Operating-system permissions for collecting CPU, memory, disk, disk I/O, and agent status metrics.
Notification routing for CPU, memory, disk, or custom threshold alerts.

Permission requirement

Use a Bitaic role that can install agents and configure hosts, plus operating-system permissions that allow resource metrics and agent status to be collected on the monitored server.

What Bitaic Checks

CPU utilization.
Memory utilization.
Disk capacity or disk usage.
Disk I/O metrics.
Host identity and Health Monitoring agent status.
Real-time and historical health metrics in the Bitaic dashboard.

Configuration Example

Configuration note

Health Monitoring uses metric toggles in health-agent-config.yml. Configure CPU, memory, disk, disk I/O, and custom health thresholds from the dashboard or configuration surface.

health-agent-config.yml
metrics:
  cpu_usage: true
  memory_usage: true
  disk_usage: true
  disk_io: true

Setup Flow

Confirm the host is inside the supported OS matrix.
Install the Health Monitoring agent on the host.
Enable the required CPU, memory, disk usage, and disk I/O metrics.
Configure safe threshold values for each monitored metric in the dashboard or configuration surface.
Start the agent and confirm the dashboard shows host identity, agent status, recent metrics, and alert state.

Data, Alerts, And Dashboard Output

Output	Purpose
CPU utilization	Shows processor load so teams can identify sustained resource pressure and noisy processes.
Memory utilization	Shows memory pressure before applications begin swapping, degrading, or failing.
Disk usage	Shows capacity risk before full disks interrupt logging, databases, queues, or application writes.
Disk I/O	Helps identify storage bottlenecks that can make otherwise healthy services feel slow.
Host identity	Connects metrics to the monitored server or host.
Agent status	Confirms whether Bitaic is receiving fresh health telemetry from the host.
Alert threshold state	Shows whether CPU, memory, disk, disk I/O, or custom health thresholds are clear, warning, or firing.

Bitaic alerts when CPU, memory, disk, disk I/O, or configured health thresholds exceed safe limits. Alert routing uses the same notification and incident integrations as other Bitaic monitoring products.

Dashboard Views

Current host status with the latest CPU, memory, disk, disk I/O, and agent-state values.
Historical metric trends that help teams compare current resource pressure with prior behavior.
Threshold and alert-state views that show which metric crossed a safe limit and when the alert began.

CLI And API

CLI support includes health install, start, agent status, and health status commands. API support includes retrieving health metrics and managing health thresholds.

bitaic install agent health
bitaic agent start health
bitaic agent status health
bitaic health status

$ bitaic health status
host: app-server-01
agent_status: running
cpu_usage: 42%
memory_usage: 68%
disk_usage: 71%
disk_io: normal
alert_state: clear
checked_at: 2026-08-18T14:30:00Z

Troubleshooting

Symptom	Likely cause	Next check
Metrics stop updating	The Health Monitoring agent may be stopped, disconnected, or unable to send telemetry.	Run `bitaic agent status health`, confirm network access, and review host permissions.
CPU or memory alert fires	The host exceeded its configured threshold or a workload is using more resources than expected.	Compare recent metric history with deployments, scheduled jobs, and application telemetry.
Disk usage alert fires	Available disk capacity may be below the configured safe limit.	Check logs, temporary files, database growth, queue backlogs, and cleanup jobs on the host.
Disk I/O looks unhealthy	Storage latency, queue depth, or throughput may be affecting host performance.	Review disk I/O trends next to application latency and host-level workload changes.
Host is missing from the dashboard	The agent may not be installed, authenticated, started, or associated with the expected account.	Verify installation, configuration, agent status, and dashboard organization or project selection.