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

 

 

Consumption Analytics Documentation

Home > Cloud Cruiser 3 > Batch XML Reference > Transform processors > ConvertSnapshotToPeriod

ConvertSnapshotToPeriod

Table of contents
No headers

Fills in missing usage start or usage end depending on configuration.

NOTE: For event data that contains the future state of resources, it is recommended to use the ConvertEventsToAllocations transform instead of ConvertSnapshotToPeriod . For example, a modify event that contains information on resources after the modification took place.

Class

<bean class=”com.cloudcruiser.batch.transform.ConvertSnapshotToPeriod”>

Properties

<property name="keyIdentifiers" value="keyIdentifiers
" />

Sets one or more identifier names used to correlate records. Ideally, this would only be @acctid . Otherwise, sufficient identifiers should exist to provide correlation at the lowest account level. This defaults to @acctid .

<property name="stickyIdentifiers" value="false" />

Sets a flag to control adding missing identifiers from records already processed for same key values. Set to true to carry over missing identifiers.

<property name="stickyResources" value="false" />

Sets a flag to control adding missing resources from records already processed for same key values. Set to true to carry over missing resources.

<property name="useBeginState" value="true" />

Sets which snapshot record for a period dictates state for that period. By default, the ending snapshot is assumed to hold state that applies to the period. Set to true when the beginning snapshot has the proper state for the period.

For more information, see See useBeginState Table..

useBeginState Table

The following table compares the default behavior with convertSnapshotToPeriod ’s useBeginState property is set to true .

Default

useBeginState true

All records have the same set of key identifiers

All records have the same set of key identifiers.

Records with start time and no end time indicate created transactions.

Records with start time and no end time indicate created or modified transactions.

Records with end time and no start time indicate deleted or modified transactions.

Records with end time and no start time indicate deleted transactions.

Deleted or modified transactions include resource values representing previous state.

Created or modified transactions include resource values representing future state.

Resources are only assumed to exist up to the most recent snapshot in records processed.

Resources are assumed to exist until end of the period unless there is a delete transaction.

Records include a complete inventory snapshot on or after end-of-day (23:59:59) on select date.

Records include a complete inventory snapshot on or before end-of-day (00:00:00) on select date.

NOTE: If inventory snapshot is not available, then all historical data must be processed.

The period of interest is assumed to be the select date for the job (24 hours). If no provision record exists in the data for a particular set of key identifiers, then resources are assumed to have existed at start of day (00:00:00).

Resources are only assumed to have existed up to the last snapshot in the records processed. Only the allocations that are determined to have existed on select date are accounted for.

Spring Batch XML Example

The following sample XML piece converts service requests to subscription periods, where provider correlation records should be excluded from this transform because their start times may throw off period resolution intended for requests:

<bean class="com.cloudcruiser.batch.transform.ConvertSnapshotToPeriod">
   <property name="active" value="true" />
   <property name="keyIdentifiers" value="id" />
   <property name="useBeginState" value="true" />
</bean>
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
© Copyright 2018 Hewlett Packard Enterprise Development LP