Health Monitoring Agent
The Health Monitoring Agent provides continuous monitoring of server performance metrics, including CPU usage, memory consumption, disk usage, disk I/O, and agent status.
Key Features
- CPU usage tracking: monitor real-time CPU utilization to detect sustained resource pressure.
- Memory usage: track memory consumption before applications degrade or fail.
- Disk usage and disk I/O: monitor storage capacity and storage bottlenecks.
Supported Hosts
Install the Health Monitoring Agent on supported Linux server hosts or Windows Server 2019 and 2022 hosts. macOS is CLI-only for Health Monitoring workflows at launch.
Runtime Model
- Install or upgrade with
sudoor root on Linux and local Administrator on Windows Server. - Run ongoing collection as
bitaic-healthon Linux orNT SERVICE\BitaicHealthAgenton Windows Server. - Allow outbound HTTPS on TCP 443 to
api.bitaic.comandingest.bitaic.com. Install and update workflows may also reachdownloads.bitaic.com. - Health Monitoring does not require inbound firewall rules, SSH keys, interactive shell access, packet capture, kernel modules, or database credentials.
Installation
To install the Health Monitoring Agent:
bitaic install agent healthConfiguration
Configure collection, metrics, and initial threshold seeds in health-agent-config.yml.
agent:
collection_interval_seconds: 60
local_buffer_hours: 24
metrics:
cpu_usage: true
memory_usage: true
disk_usage: true
disk_io: true
thresholds:
cpu_utilization_percent:
warning: 80
critical: 95
memory_utilization_percent:
warning: 85
critical: 95
disk_used_percent:
warning: 85
critical: 95
disk_io_utilization_percent:
warning: 80
critical: 95cpu_usage: enable CPU usage monitoring.memory_usage: enable memory usage tracking.disk_usage: enable disk usage tracking.disk_io: enable disk I/O monitoring.thresholds: seed warning and critical percentage thresholds for CPU utilization, memory utilization, disk used, and disk I/O utilization. Ongoing threshold edits are managed from the dashboard or API.
Freshness
Metrics collect every 60 seconds by default. Bitaic marks telemetry fresh when the latest heartbeat and metric sample are no more than two collection intervals old, stale after three missed intervals, and unknown before first telemetry or unresolved host identity.
Usage
Start the agent with:
bitaic agent start healthCheck the status:
bitaic agent status healthAccessing Health Data
Review real-time health metrics in the Bitaic dashboard or query specific metrics through the CLI.