Skip to main content

Unified Monitoring

Cloudaware Unified Monitoring centralizes metrics and events from cloud services and Breeze Agent–powered hosts. It enriches every signal with Cloudaware CMDB context so you can view infrastructure, applications, and business impact in a single operational view.

info
  • Audience: Cloudaware administrators, cloud/platform and SRE teams, NOC teams, application owners
  • Outcome: Unified cross‑cloud monitoring and alerting with consistent coverage reporting, dashboards, and runbooks for triage and recurring monitoring workflows

Use Unified Monitoring when you want to:

  • Consolidate health signals from cloud-native services, hosts, network devices, and third-party monitoring tools.
  • Identify resources that are not monitored or have incomplete alerting coverage.
  • Standardize alert formats, routing, maintenance windows, and escalation workflows.
  • Explore monitoring data by application, environment, account, owner, or business unit.
  • Monitor managed cloud services where host agents cannot be installed.
  • Analyze performance trends and retained metrics for troubleshooting and capacity planning.
  • Extend monitoring coverage without replacing existing monitoring platforms.

Core Capabilities​

Cloudaware Unified Monitoring provides:

  • Multi-source telemetry ingestion – metrics, events, alerts, and status data from cloud-native services, hosts, network devices, and supported third-party monitoring tools consolidated into a shared model.
  • Host-level monitoring – operating system and performance telemetry collected through Breeze Agent and supported monitoring components.
  • Managed-service monitoring – cloud-native metrics collected for databases, load balancers, storage, data platforms, and other services where agents cannot run, including Amazon CloudWatch, Azure Monitor, and Google Cloud Monitoring.
  • CMDB-based enrichment – monitoring signals associated with resources, applications, environments, owners, accounts, regions, tags, and relationships.
  • Coverage analysis – monitored, partially monitored, and unmonitored resources identified across applications, environments, accounts, and service types.
  • Unified alerting – policies and thresholds, routing rules, maintenance windows, silences, and escalation paths applied across supported sources.
  • Support for third-party monitoring integrations – summary metrics, events, incidents, and monitoring status imported from existing platforms through notification channels and webhooks.
  • Dashboards and trend analysis – health, performance, alert volume, coverage, and historical trends available through dashboards, KPIs, and dashboard templates.
  • Operational workflows – alerts connected to notifications, ITSM systems, incident-management tools, webhooks, and runbooks for recurring operations.

How Unified Monitoring Works​

Cloudaware Unified Monitoring follows a telemetry-to-response workflow:

  1. Identifies monitorable resources. Cloudaware CMDB and connected integrations provide resource inventory, ownership, application, environment, account, and relationship context.
  2. Collects telemetry. Cloud-native services, Breeze Agent, Zabbix, and supported third-party tools send metrics, events, alerts, and status data into Cloudaware.
  3. Normalizes and enriches signals. Monitoring data is associated with CMDB context such as application, environment, owner, account, region, tags, and related resources.
  4. Evaluates alert policies. Unified Monitoring applies thresholds, conditions, routes, maintenance windows, silences, and escalation rules across supported sources.
  5. Surfaces dashboards and coverage views. Teams review health, performance, alert volume, monitoring coverage, and historical trends through dashboards and reports.
  6. Routes response workflows. Alerts can trigger notifications, incidents, tickets, webhooks, and runbooks for the teams responsible for affected services.
  7. Supports monitoring optimization. Coverage reports, dashboards, and CMDB queries help teams identify monitoring gaps, tune alert thresholds, reduce noise, and extend coverage to additional resources and services.

Monitoring Sources and Alerting​

Cloudaware Unified Monitoring combines telemetry from several source types.

Cloud-Native Monitoring Services​

Cloud provider services supply metrics for resources where host-based monitoring is unavailable or unnecessary.

Examples include:

These sources are commonly used for managed services such as databases, load balancers, storage services, and data platforms.

Host and Network Monitoring​

Breeze Agent provides host inventory and telemetry and can support deployment and operation of monitoring components.

Zabbix is used as the default engine for supported agent-based monitoring of servers and network devices.

Third-Party Monitoring Platforms​

Unified Monitoring can work alongside existing monitoring platforms by ingesting metrics, events, incidents, or status data through dedicated integrations or webhooks.

Supported patterns can include integrations with platforms such as:

See Ingestion and Integrations for current source support and configuration guidance.

Alerting and Routing​

Unified Monitoring provides a consistent alerting layer across supported telemetry sources.

Alerting workflows can include:

  • Threshold and condition policies.
  • Routing by application, environment, team, owner, or severity.
  • Maintenance windows and silences.
  • Escalation rules.
  • Email and webhook notifications.
  • PagerDuty
  • Slack
  • Jira
  • ServiceNow

CMDB relationships and ownership data help route alerts to the appropriate teams and provide context about affected applications and dependent resources.

Relationship to Other Modules and Services​

Unified Monitoring works together with:

Explore the Unified Monitoring Documentation​

Use these guides together as the Cloudaware Unified Monitoring documentation set.

Prepare Unified Monitoring​

  1. Review requirements. Confirm prerequisites for cloud integrations, Breeze Agent, Zabbix, network access, permissions, security, and operational readiness.

  2. Configure ingestion. Connect cloud services, hosts, and supported third-party monitoring sources.

  3. Understand metrics and events. Review the data model for metrics, events, labels, tags, retention, rollups, and correlation.

Configure Monitoring and Alerting​

  • Alerting: Define policies, thresholds, routes, channels, maintenance windows, silences, and escalation paths.
  • Dashboards: Build dashboards for health checks, triage, trends, coverage, and reporting.
  • Integrations: Connect cloud monitoring services, notification channels, webhooks, and incident-management systems.

Operate and Improve Monitoring​

  • Operations: Manage access control, data handling, scale, governance, monitoring exceptions, and recurring operations.
  • Playbooks: Follow practical workflows for source onboarding, golden signals, alert tuning, coverage analysis, and noise reduction.
  • Reference: Review limits & quotas.
  • FAQ: Find answers about Unified Monitoring scope, Zabbix, retained data, alerts, integrations, and ownership.