Skip to main content

Health & Status

Use this guide to validate Breeze Agent health, confirm host check-ins, review scheduler and log status, and troubleshoot unhealthy or stale hosts.

Check Agent Health on the Host​

Linux and macOS​

  • Verify the scheduler:
    • systemctl status breeze-agent.timer (preferred), or
    • cat /etc/cron.d/breeze-agent for cron‑based setups.
  • Check recent runs:
    • journalctl -u breeze-agent.service --since "15 minutes ago" (if using systemd units), or
    • Inspect /opt/breeze-agent/var/log/breeze-agent.log for the latest entries.

Windows​

  • Open Task Scheduler and verify:
    • Task Breeze Agent exists.
    • Last Run Time and Last Run Result show successful, recent runs.
  • Confirm logs at C:\\Program Files\\Breeze\\agent.log are updating on the expected cadence.

Check Breeze Health in Kubernetes​

Verify the Breeze DaemonSet:

  • Run kubectl get ds -n <namespace> and confirm that DESIRED, CURRENT, and READY match.
  • Run kubectl logs -n <namespace> <breeze-pod> and check for recurring errors.

Check Agent Status in Cloudaware​

In Cloudaware CMDB:

  • Use the default list views (for example, BREEZE: ACTIVE) on servers and Kubernetes nodes to:
    • Filter assets by the Breeze: Last Update column in the view.
    • Copy the default view, adding the filter 'Breeze Is Active' equals FALSE. Identify stale or never‑seen hosts.

Investigate Unhealthy or Stale Hosts​

If a host is not reporting as expected:

  • Verify OS‑level scheduling (timer/cron or Task Scheduler) and logs on the host.
  • Confirm outbound HTTPS connectivity to breeze-server.cloudaware.com (and proxies, if used).
  • Check configuration and tags:
    • Ensure the agent certificate is valid and not expired.
    • Confirm tags and descriptors are set as expected in etc/tags or env files.
  • Use the guidance in Troubleshooting for common failure patterns.