Breeze Agent FAQ

This FAQ answers common questions about Cloudaware Breeze Agent.

Does the Agent Need Root/Administrator Access?

For discovery, no. The agent can run without elevated privileges. For management plugins (e.g., patching, IDS, scanner deployment), root/Administrator is required.

Is It Secure? Where Is Data Sent?

All communications use mutual TLS and signed payloads. Data flows into Cloudaware running on the Salesforce Platform. See Security for details.

I Installed Breeze but Don’t See Data in the CMDB Yet. How Long Does It Take?

Initial enrichment can take up to several hours depending on estate size and collection cadence. Use CMDB Default list views (for example, BREEZE: ACTIVE) and Breeze health guide to track check‑ins.

Do You Update Breeze?

Yes. Updates occur as planned rollouts or when additional functionality is requested. The agent supports OTA updates for agent, plugins, and configurations. See Upgrades & Uninstall for details.

Can I Control Which Plugins Run?

Yes. Only approved plugins are executed per your configuration and rules. See Configuration and the Config for plugin settings.

Do I Need to Reinstall Breeze When Baking New Images From an Existing One?

No. You can bake the agent into images (AMI/VM templates); it will self‑configure at first run. For common patterns, see Breeze deployment patterns and Fleet Deployment.

Can the Agent Be Installed on Physical (On‑Prem) Servers?

Yes. Ensure outbound HTTPS to the Breeze server (see Ports & Endpoints). For internal systems (vCenter, AD, SCCM), the agent can act as a local collector and transmit data to the CMDB.

Can Breeze Establish Secure Tunnels to Customer Environments?

Yes, via TunHub integration, Breeze can configure OpenVPN clients to create secure tunnels to backend services.

How Much Network Traffic Does Breeze Generate?

On average ~50 KB per report. With a 15‑minute cadence, ~4.8 MB per host per 24 hours.