Skip to main content

Events

Events represent discrete occurrences in time — such as alerts firing or resolving, deployments, configuration changes, security findings, or external incidents coming from third‑party monitoring tools. Unified Monitoring treats events as first-class signals that can be correlated with metrics and CMDB records.

Event Sources​

Typical event sources include:

  • Alert policies defined in Unified Monitoring.
  • Status updates from Zabbix and other monitoring systems.
  • Incidents and checks from tools like New Relic, Pingdom, Datadog, SolarWinds, Nagios, Sensu, and others.
  • Change or deployment events from CI/CD pipelines or ITSM tools.
  • Security or compliance findings from other Cloudaware modules.

Event Structure​

At a high level, each event carries:

  • A timestamp and source.
  • A type (for example, alert, change, incident, health check, security finding).
  • A severity and status (for example, warning, critical, resolved).
  • Labels referencing the affected CI(s) — for example, account, region, application, environment, and resource IDs.
  • Optional payload fields with additional metadata.

Design event payloads so that they are useful in dashboards, searches, and alert workflows without being excessively verbose.

Correlating Events with Metrics​

Use events to provide context around metric behavior:

  • Annotate dashboards with deployment or change events.
  • Use incidents from external tools as triggers for Unified Monitoring playbooks.
  • Combine events with metrics to detect outages, regressions, or capacity issues.
On this page