Data Health

Unified Monitoring is only as reliable as the data it receives from data sources.

Use this guide to ensure that metrics and events are current, complete, and aligned with expectations.

What to Check

When onboarding or troubleshooting, validate:

Freshness – metrics should update at the expected cadence (for example, every minute or every five minutes, depending on the source).
Completeness – key hosts and services should have at least baseline metrics (CPU, memory, disk, availability).
Coverage – all critical applications, accounts, and regions should be monitored. CMDB list views and reports can highlight missing sources.
Consistency – metric names, units, and labels should be standardized across sources.

No data for a host
- Check that Breeze Agent is installed and healthy.
- Confirm that the host appears in CMDB and is correctly associated with an account and application.
- Make sure the Zabbix integration is configured and enabled.
No metrics for a managed service
- Confirm that the relevant cloud integration (AWS, Azure, Google Cloud) is configured.
- Verify permissions allow Cloudaware to read metrics for that service.
- Ensure the service is in a region/account covered by the integration.
Gaps or delays in metrics
- Check network connectivity from agents and collectors to Cloudaware.
- Review provider‑side throttling or rate limits.
- Validate that you have not exceeded any limits described in Limits & Quotas.

Review data health regularly, especially after adding new integrations or accounts.
Include data‑health checks as part of onboarding playbooks and change procedures.
Use CMDB tagging so that you can easily filter for resources that should be monitored but are not yet sending data.