Skip to main content

Unified Monitoring Requirements

Unified Monitoring builds on Cloudaware’s CMDB discovery, Breeze Agent, and cloud integrations. This guide summarizes the main prerequisites so you can confirm readiness before enabling monitoring at scale.

Core Platform Prerequisites​

Before you begin, ensure that:

  • Cloud accounts are connected to Cloudaware through the relevant integrations, such as AWS, Azure, and Google Cloud.
  • CMDB is discovering compute instances, managed services, and key network components for those accounts.
  • Breeze Agent is installed on hosts you want to monitor.
  • At least one supported telemetry source is available, for example, Zabbix or other tools you already use.

Breeze Agent and Zabbix​

For host‑level monitoring:

  • Install Breeze Agent on supported operating systems and confirm it can reach the required Cloudaware endpoints.
  • Configure the Zabbix integration for each environment or account, as required by your deployment model.
  • Verify that Breeze-managed hosts are discovered correctly and associated with the expected monitoring configuration.

This combination provides host-level CPU, memory, disk, process, and service telemetry correlated with CMDB configuration items.

Cloud Provider Requirements​

Unified Monitoring uses cloud-native telemetry for managed services and other resources where agents cannot be installed.

AWS​

  • Ensure the AWS accounts you want to monitor are integrated with Cloudaware.
  • Confirm that Cloudaware has the IAM permissions required to discover resources and read relevant CloudWatch metrics and status data.
  • Enable any additional service-specific telemetry required for resources such as Application Load Balancers, RDS, Redshift, and other managed services.
  • If you also use AWS-native agents (for example, CloudWatch Agent), align tagging and resource metadata with your CMDB strategy so coverage analysis remains accurate.

See also: Collector Policy Part #1 and Cloudaware Collector IAM Policy for Unified Monitoring.

Azure​

  • Ensure the Azure subscriptions you want to monitor are integrated with Cloudaware.
  • Enable Azure Monitor for the services you want to include.
  • Configure Diagnostic Settings and related data pipelines where logs or platform diagnostics are required.
  • Confirm that Cloudaware has access to the relevant subscriptions, resource groups, and monitoring resources.

See also: Azure – Least Privilege

Google Cloud​

  • Ensure the Google Cloud projects you want to monitor are integrated with Cloudaware.
  • Enable Cloud Monitoring for the target projects.
  • Confirm that the Cloudaware service account has permission to read the required metrics for those projects and any related monitoring scopes used in your environment.

See also: GCP – Least Privilege

Other Environments​

For VMware, on‑prem data centers, and other platforms, use:

Network and Security Requirements​

To allow metrics and events to flow into Cloudaware:

  • Permit outbound HTTPS traffic from Breeze Agent hosts to the required Cloudaware endpoints.
  • Ensure Zabbix servers can reach Cloudaware APIs where needed, and that Cloudaware can access Zabbix APIs if your integration model requires it.
  • Allow Cloudaware connectors and collectors to reach cloud provider APIs.

Review these requirements against your organization’s firewall, proxy, and egress policies. For environment-specific details, see the Breeze Agent requirements and the applicable integration guides.

Minimum Starting Point​

To begin with a limited but useful deployment, start with:

  1. A small set of AWS, Azure, or GCP accounts integrated with Cloudaware.
  2. Breeze Agent installed on a representative group of servers.
  3. One or two monitoring sources, such as Zabbix and an existing APM or synthetic monitoring tool.

You can then expand Unified Monitoring coverage across additional accounts, services, and regions.