Cloud Cruiser became HPE Consumption Analytics on Nov. 1, 2018. You'll still see the old name in places while we update this site.

 

 

Consumption Analytics Documentation
Home > Documentation for older versions > Cloud Cruiser 4 > Administering > Managing schemas

Managing schemas

The Schema Management page lets you manage the data schemas to which you publish the data you collect with HPE Consumption Analytics Portal. When HPE Consumption Analytics Portal runs a charge job, each service is compared against data in schemas to determine how to charge for that service. Each schema has a corresponding view in the HPE Consumption Analytics Portal database that you can use to create reports.

To work with schemas, navigate to the Data > Setup > Schema Management page.

Key dimensions and required fields

Each schema can include one or more key dimensions, which combine to form a unique object in the schema. Each schema can also define one or more required fields, which must be mapped to a worksheet column when defining a Publish Data step in a workbook. For more information about using the Publish Data step, see Publishing data to a schema.

Schema options

Each schema includes a Yes/No setting for the following options:

  • Requires Account ID: Determines whether each row in the schema must include an account ID. When set to Yes, any Publish Data step that publishes to the schema includes an Account ID table, which enables you to map collected data in the worksheet to your account structure. For more information about account structures, see Working with account structures.
    publishToInfrastructure.jpg
  • Passthrough: Determines whether the measures in the schema include pricing information provided by the data source. When set to Yes, each measure published to the schema must include a rate or cost (in addition to a quantity value).

Default schemas

HPE Consumption Analytics Portal includes the following schemas, each tailored for a particular use:

Schema Description
APC

Use the Azure Public Cloud (APC) schema for Microsoft Azure data. This schema has no key dimensions. ComputedServiceName is a required field.
AWS

Use the AWS schema for Amazon Web Services usage data. This schema has no key dimensions or required fields.
Infrastructure

Use the Infrastructure schema for common cloud infrastructure pieces, such as VMs, storage pools, and databases. This schema is more general than the other schemas. If you are collecting data only for one type of provider, such as AWS or Microsoft Azure, use a more specific, vendor-specific schema. If you have a more diverse environment, and want to be able to use a single report to compare VM usage from several providers, use a more general schema, such as Infrastructure.

This schema has no key dimensions or required fields.
Network

Use the Network schema for general network infrastructure data. The key dimension is Name. The required fields are:

  • Name
  • Bytes In
  • Bytes Out
  • IP Address
Storage

Use the Storage schema for general VM storage data. This schema has no key dimensions. The required fields are:

  • Name
  • Disk Allocated
  • Disk Capacity
  • Disk Used
Virtual Machine Use the Virtual Machine schema for general information about VMs and their usage. The key dimensions are VM Id and VM Name. These dimensions are also required fields.
Windows Azure Pack

Use the Windows Azure Pack schema for subscription and usage data from your Windows Azure Pack environment. The key dimension is Id. The required fields are:

  • Id
  • Provider Name

Creating a new schema

If one of the default schemas does not suit your needs, create a new schema.

To create a schema

  1. Open the Data > Setup > Schema Management page.
  2. In the list of schemas, right-click and select New Schema.
    The Add New Schema dialog box opens.
  3. Enter a Name for the schema, provide Comments that describe the purpose of the schema, and then click OK.
    The new schema opens, with one empty field.
  4. Define the first field in your schema:
    • Name: The name of the field.
    • Description: (Optional) A description of the field.
    • Type: Either dimension or measure. Dimensions are fields that contain qualitative or categorical information. They provide context around the value of a measure, answering questions like "What type?" and "When?" Measures are numeric fields containing quantitative information. They are the "how much?" information.
    • Units: (Optional, and for measures only) The units of measurement, such as Count, GB, or Minutes.
    • Measurement: (For measures only) The method used to measure the incoming data, either Allocated or Metered. Allocated measures are defined by how long it is made available to be used, such as VM-hours. Metered measures are defined by the amount used, such as bytes of data transferred. 
    • Key: (Optional, and for dimensions only) Select the checkbox to indicate that the field should be used to define a unique row of data in the schema. You can make multiple fields key fields.
    • Required: (Optional) Select the checkbox to make the field required when publishing data to the schema from a workbook.
  5. If you want to add another field, click New Field.
  6. If you want each row in the schema to include an account ID with published data, set the Requires Account ID field to Yes. For more information, see Schema options.
  7. If you want the measures in the schema to include pricing information provided by the data source, set the Passthrough field to Yes. For more information, see Schema options.
  8. Click Save.
    You can now publish data to the schema.
Last modified

Tags

Classifications

This page has no classifications.
    Powered by MindTouch ®