Skip to main content

Schema Reference

This guide provides a high‑level view of the main Cost Management datasets and how they relate to CMDB and other modules.

Core Cost Datasets​

While actual object names and fields may vary by implementation, Cost Management typically exposes:

  • Billing line items.
    • Raw or normalized records for cloud provider usage and charges.
    • Include provider identifiers (account, subscription, project), service, usage type, region, and time period.
    • Contain multiple cost metrics (for example, list/on‑demand cost, effective cost, blended rates).
  • Aggregated cost tables.
    • Pre‑summarized views by day, month, account, BU, application, environment, or customer.
    • Used for dashboards, KPIs, and exports where line‑item detail is not required.

Both datasets are enriched with CMDB context (applications, owners, environments) via allocation and business mapping.

Allocation and Business Mapping Datasets​

To support allocation and showback/chargeback, Cloudaware Cost Management uses:

  • Allocation mappings.
    • Rules and lookup structures that map accounts, subscriptions, projects, tags, and other metadata to business dimensions (BU, product, team, customer).
    • Often implemented as mapping tables or configuration objects.
  • Shared‑cost definitions.
    • Records describing how shared or platform costs are distributed (for example, fixed percentages, usage‑based splits).
  • Model configuration.
    • Objects that capture showback/chargeback models, including rate types (effective vs. on‑demand), scopes, and hierarchies.

See Allocation and Showback & Chargeback for conceptual details.

Optimization and Commitment Datasets​

Optimization features rely on:

  • Rightsizing candidates.
    • Records linking resources (instances, databases, etc.) to utilization metrics, cost, and recommended target sizes.
  • Waste findings.
    • Policy outputs for idle or orphaned resources, including potential savings estimates.
  • Commitment and reservation data.
    • Objects representing RIs, Savings Plans, reservations, CUDs, and their usage.
    • Include coverage, utilization, and effective‑cost metrics by service, region, and scope.

These datasets drive optimization and commitment planning, as well as reporting.

Budgets, Forecasts, and Anomalies​

Cloudaware Cost Management also includes:

  • Budgets. Planned spend per scope and period, with thresholds for alerts.
  • Forecasts. Projected spend based on historical data and modeled changes.
  • Anomalies. Detected deviations from expected spend or usage patterns, with links to affected scopes and drivers.

Budgets and anomalies often reference the same scopes used in allocation and business mapping to maintain consistency.

Working with Schemas​

When building reports, dashboards, or integrations:

  • Use exact object and field names (schema reference can be found in Cloudaware Setup → Objects Manager/Objects).
  • Favor summarized or aggregated tables for most reporting; use line‑item detail only when necessary.
  • Reuse business dimensions (BU, application, environment, customer) consistently across cost, allocation, optimization, and showback/chargeback objects.