Skip to main content

Advanced Analytics Requirements

This guide summarizes what you need in place before enabling Cloudaware Advanced Analytics and rolling it out to users.

Platform & Licensing Prerequisites​

Before you begin, ensure that:

  • Salesforce CRM Analytics is enabled and licensed. Your Salesforce org must include an Analytics Platform license (or equivalent) and associated permission sets (for example, CRM Analytics Platform Admin/User). See Operations – RBAC for verification steps.

  • Cloudaware is integrated with your Salesforce org. The Cloudaware account should be connected to the Salesforce environment where CRM Analytics runs, using supported integration patterns and identities.

  • Analytics users and integration users have appropriate access. Assign Analytics Platform licenses and CRM Analytics permission sets to:

    • At least one integration/admin user that owns datasets, recipes, and dashboards.
    • Viewer/editor users who will access analytics dashboards. See Operations – RBAC for details.

Cloudaware Module Readiness​

Advanced Analytics depends on signals from other Cloudaware modules. For useful coverage, confirm that:

  • CMDB is onboarded CMDB should be discovering core cloud accounts, subscriptions, projects, and on‑prem inventory so analytics can slice by account, application, environment, owner, and other dimensions.

  • Key modules are enabled and healthy Depending on your use cases, enable and validate:

    • Compliance Engine for policy runs and violation events.
    • Cost Management for cost and usage metrics.
    • Unified Monitoring for alert and incident signals.
    • Other modules (for example, Log Management, Vulnerability Management) as applicable. Advanced Analytics can surface only the events and metrics that these modules emit.

  • Core integrations are configured Cloud, monitoring, security, and ITSM integrations should be connected using least‑privilege identities so their data appears in CMDB and related modules; see Integrations.

Identity, RBAC, and Governance​

Because Advanced Analytics is built on Salesforce, you must:

  • Configure permission sets, apps, and folders in CRM Analytics so that:
    • Admins can manage datasets, recipes, and dashboards.
    • Users can view dashboards without over‑privileged access.
  • Align dataset‑level row‑level security (sharing inheritance, security predicates) with Cloudaware scopes and CMDB ownership; see Operations – RBAC and Data Model – Attributes.
  • Establish basic data governance practices for analytics datasets (field naming, ownership, and documentation); see Data Governance.

Data Ingestion & Data Manager​

To ensure analytics data is collected and maintained correctly:

  • Use Data Manager as the control plane:

    • Connections to Salesforce objects and external sources are defined and monitored in Data Manager → Connections.
    • Recipes and (legacy) dataflows that populate Advanced Analytics datasets are visible in Jobs Monitor and Recipes. See Data Manager and Data Preparation.

  • Confirm event and metric sources are enabled. The event pipelines that feed Advanced Analytics should be configured and visible in the ingestion layer; see Event Sources.

  • Plan for data health monitoring. Establish a basic process to watch dataset freshness, ingestion success, and drop/error rates using Data Manager and any dedicated dashboards; see Data Health.

Capacity, Limits, and Scale​

Advanced Analytics relies on Salesforce CRM Analytics limits for storage and processing. Before large rollouts or historical backfills:

  • Check CRM Analytics usage in Data Manager → Usage and understand your org’s limits for:

    • Dataset rows.
    • External data uploads (for example, BigQuery or other external sources). See Limits & Quotas.

  • Design datasets and recipes with scale in mind:

    • Use subject‑area‑specific datasets (adoption, reliability, compliance, cost) instead of a single oversized dataset.
    • Aggregate high‑volume events into daily or weekly metrics where possible.
    • Separate raw vs analytics‑ready datasets. See Performance & Scale.

  • Agree on retention expectations for events and metrics and how long you need detailed vs aggregated history. For long‑term or cross‑tool analysis, plan to use warehouse/BI exports instead of keeping all history in CRM Analytics; see Integrations – Data Warehouse.

Network and Environment Assumptions​

In addition to the requirements for each Cloudaware module and integration:

  • The Salesforce org hosting CRM Analytics must be reachable by Cloudaware according to your integration design.
  • Any external systems used for warehouse exports or BI tools (for example, Snowflake, BigQuery, Tableau) must meet their own network and authentication requirements.

Coordinate specifics (endpoints, proxies, IP ranges) with your Cloudaware representative if your environment is highly restricted.

Next Steps​