Ingestion
In Unified Monitoring, ingestion is the process of collecting metrics and events from cloud providers, hosts, and external monitoring systems, then normalizing and enriching them with CMDB context.
This section explains the main ingestion patterns and where to configure them.
Ingestion Patterns
Unified Monitoring supports several ways to bring data in:
- Cloud‑native monitoring services – metrics from Amazon CloudWatch, Azure Monitor, and Google Cloud Monitoring are collected via Cloudaware’s cloud integrations. See Cloud Providers.
- Host‑level telemetry via Breeze – Breeze Agent installs collectors (for example, Zabbix agents) on supported hosts to gather CPU, memory, disk, process, and service metrics. See Breeze Agent.
- Third‑party monitoring tools – events and incidents from tools such as Zabbix, Datadog, New Relic, SolarWinds, Pingdom, Nagios, Sensu, and others can be ingested via dedicated integrations or generic webhooks.
Regardless of source, data is mapped into a consistent metrics‑and‑events model so you can define policies and dashboards uniformly.
Typical Onboarding Sequence
- Connect cloud accounts (AWS, Azure, GCP) and verify that Cloudaware CMDB is discovering resources.
- Deploy Breeze Agent to hosts where you want detailed OS‑level metrics.
- Configure monitoring integrations (for example, Zabbix, Datadog, Pingdom, Nagios, Sensu) under Other Integrations or via Webhooks.
- Use Data Health to verify that metrics and events are arriving as expected.
Reading Path
Cloud Providers
Explore how metrics from AWS, Azure, Google Cloud, and other cloud platforms are collected through Cloudaware integrations.
Breeze Agent
Understand what Breeze Agent collects from hosts and how to deploy it for host-level monitoring.
Data Health
Verify that monitoring data is arriving as expected and troubleshoot common ingestion issues.