SysGuard

Use when creating structured incident alerts from SysGuard findings, health reports, log analysis, remediation failures, or operational events.

Use when checking database connectivity, running read-only diagnostic SQL, validating DSNs, or collecting small database health evidence through SysGuard.

Use when reading, statting, listing, or tailing local files for SysGuard diagnostics without modifying filesystem contents.

Use when checking host health, service health, CPU, memory, disk, network status, or determining whether SysGuard should treat a system as unhealthy.

Use when analyzing operational logs, filtering errors or warnings, summarizing incidents from log files, or finding relevant lines in SysGuard-managed logs.

Use when collecting structured CPU, memory, disk, network, service, or health-score metrics from SysGuard for dashboards or reports.

Use when diagnosing DNS, TCP connectivity, ping reachability, network interfaces, service ports, or network-related SysGuard incidents.

Use when sending SysGuard alerts, summaries, remediation outcomes, or operational messages to stdout, logs, or webhook targets.

Use when inspecting, starting, stopping, restarting, or reading logs for managed Linux/macOS services through SysGuard.