Skip to main content

Event Sources

Use this guide to understand where Advanced Analytics data comes from: which events and metrics Cloudaware collects, how they map to modules, and what you should verify when onboarding.

At a high level:

  • The application backend and UI emit usage events (logins, dashboard views, feature actions).
  • Core Cloudaware modules (CMDB, Compliance Engine, Cost Management, Unified Monitoring, and others) emit operational and coverage events.
  • Ingestion jobs and exports emit data‑quality and pipeline‑health signals.
  • Optional cloud usage feeds (for example, cost and inventory exports) contribute additional metrics.

For schema details, see Events and Metrics.

Role in Advanced Analytics​

Event sources are the raw inputs that power:

  • Engagement KPIs (DAU/WAU/MAU, session depth).
  • Adoption metrics by module and feature.
  • Operational KPIs such as Time to Detect/Recover and control coverage.
  • Data‑quality indicators like dataset freshness and ingestion success rate.

Advanced Analytics does not require you to manage these feeds individually, but you should understand which sources are in scope so you can:

  • Confirm the right modules and integrations are enabled.
  • Validate that high‑value events are actually firing.
  • Coordinate retention expectations with CRM Analytics limits.

See also:

Core Event Source Categories​

Product Usage & Engagement​

These events describe how people use Cloudaware itself:

  • User authentication and sessions: user.login, user.logout, session.start, session.end.
  • Analytics activity: dashboard.view, lens.view, report.open.
  • Configuration changes: object.create / object.update for dashboards, datasets, policies, and integrations.
  • Workflow actions: playbook runs and remediation actions.

Usage events typically originate from the application backend and UI telemetry. After normalization, they are stored in CRM Analytics datasets and exposed through:

  • Events – event taxonomy and schema.
  • Metrics – DAU/WAU/MAU and session‑level measures.

Module and CMDB Signals​

Cloudaware modules emit events based on their own domain logic. Common examples:

  • CMDB & inventory – configuration changes and state transitions for assets and applications (backed by CMDB).
  • Compliance Engine – policy evaluations, rule violations, and remediation outcomes.
  • Cost Management – cost calculations, report generations, and budget breach alerts.
  • Unified Monitoring – alert lifecycle changes, acknowledgements, and incident links.
  • Other modules such as Log Management and security tools contribute additional signals where enabled.

These events are linked back to CMDB attributes so that Advanced Analytics can slice results by account, application, team, environment, and other shared dimensions; see Attributes.

Pipelines, Ingestion Jobs, and Exports​

Ingestion pipelines and analytics jobs generate events that describe whether data is flowing correctly:

  • Connection tests and refresh runs in Data Manager.
  • Recipe and dataflow job starts, completions, and failures.
  • Export jobs for CSV/S3/warehouse outputs.
  • Validation and transformation errors during data preparation.

You use these events primarily to monitor:

  • Dataset freshness.
  • Ingestion success/failure rates.
  • Event drop rates and error counts.

They underpin the data quality & reliability KPIs described in Dashboards & Reporting KPIs and are surfaced in Data Manager; see Data Manager and Data Health.

Cloud Usage and Cost Feeds​

Some Advanced Analytics metrics rely on data that originates outside Cloudaware and is ingested via other modules:

  • Cloud usage and billing data (for example, AWS/Azure/GCP usage) brought in through Cost Management.
  • Cloud service and infrastructure telemetry collected by Unified Monitoring and related integrations.
  • Optional warehouse exports (for example, Snowflake or BigQuery) configured via Analytics connectors or external ETL tools; see Integrations and Data Warehouse.

Advanced Analytics does not duplicate the raw feeds; instead, it consumes the normalized objects and events produced by these modules so you can correlate adoption and operational outcomes with spend and coverage.

Configuration & Verification Checklist​

When enabling Advanced Analytics, confirm that:

  • Required Cloudaware modules (for example, CMDB, Compliance Engine, Cost Management, Unified Monitoring) are enabled and healthy.
  • Key integrations (cloud accounts, monitoring tools, ticketing systems) are connected and regularly syncing.
  • CRM Analytics is licensed and users have appropriate access; see Operations RBAC.
  • In Data Manager, connections, recipes, and datasets related to Advanced Analytics are present and show recent successful runs; see Data Manager.

If a particular KPI or subject area is missing data, start by checking whether its underlying module or integration is enabled and emitting events.

Retention, Granularity, and Limits​

Event and metric retention can vary by environment and subject area. In general:

  • High‑volume raw events may be stored at shorter retention or pre‑aggregated into metrics.
  • Aggregated metrics (for example, per‑day per‑module adoption) are typically kept longer for trend analysis.
  • CRM Analytics dataset limits (rows, storage, external upload volume) apply to all Advanced Analytics datasets.

To review current CRM Analytics usage and limits, see Limits & Quotas, and use Data Manager → Usage for environment‑specific details.

For concrete schemas and field‑level definitions, continue with: