Skip to main content

Agents & Telemetry

Use this guide to understand how Breeze Agent serves as the primary telemetry source for Cloudaware Patch Management.

What Breeze Collects for Patching​

Breeze Agent discovers installed and upgradable packages and reports package inventory data to the CMDB.

On supported hosts, Breeze typically reports:

  • Installed package versions.
  • Available updates from OS repositories.
  • Whether a package update is security‑related where that information is available.
  • OS metadata such as distribution and version.

This data is used to calculate patch eligibility, outstanding patches, and compliance KPIs.

Automation​

Cloudaware uses Breeze plugins and helper scripts to prepare and execute patching cycles:

  • Breeze plugins such as os_updater (Linux) and os_updater_win (Windows) perform patch installation on target hosts.
  • On the last Repo Day of the cycle, Cloudaware prepares a full patching cycle for all environments using:
    • Repo Day source data
    • CMDB reports exported for the relevant systems and environments
    • Ruby scripts and helper tooling

These implementation details may vary by customer. However, Cloudaware aims to automate as much of the preparation, execution, and reporting as possible while keeping staged rollout decisions and required approvals under the customer’s control.

Other Inputs​

Cloudaware Patch Management can also use:

  • Cloud provider metadata (for example, instance type, region, auto‑scaling group) to drive patch group definitions.
  • Vulnerability data to highlight which missing patches address specific CVEs.