Consumption Analytics Documentation

Home > Release Notes > Cloud Cruiser 3.5 Release Notes

Cloud Cruiser 3.5 Release Notes

This section contains the cumulative release notes for Cloud Cruiser version 3.5.x. The current release is version 3.5.0.

All documentation articles updated for this release have the tag version_3.5List these articles.

What's new

The following features are new or enhanced in Cloud Cruiser version 3.5.0.

Use the REST API with translation tables

The Cloud Cruiser REST API now includes methods for getting, deleting, importing, and exporting translation tables. The reference documentation for these methods is at Translation tables.


The following enhancements are made to collectors or tasklets that participate in collection in this release.

OpenStack Ceilometer enhancements

The following enhancements are made to the OpenStack Ceilometer Collector in this release:

  • The collector can now use a data source that requires an SSL connection without you explicitly importing and trusting public certificates.
  • You can collect more resource metadata by setting the new includeMeta property to true.
  • The feed configuration now has the following date and time defaults, so you no longer need to explicitly set them:
    • <property name="dateTimeZone" value="UTC" />

    • <property name="dateTimePattern" value="yyyy-MM-dd'T'HH:mm:ss" />

    • <property name="datePattern" value="yyyy-MM-dd'T'HH:mm:ss" />

OpenStack AMQP enhancements

The following enhancements are made to the OpenStack AMQP Collector in this release:

  • The collector can now parse data in multiple timestamp formats when you collect mixed event types. The new alternateTimestampPatterns property of AMQPConsumerTasklet, enables you to specify a list of event types, each with its own pattern.
    For a usage example of the new property, see the sample job <install_dir>/job_samples/nova_event_listener.xml or the JavaBean Reference documentation at <install_dir>/docs/api/batch/com/cloudcruiser/batch/collect/amqp/AmqpConsumerTasklet.html.
  • You can now create a managed AMQP data source instead of maintaining credentials in multiple, unsecure job XML files.

Read JSON lists

The JSON Collector can now map data from lists of both objects and intrinsics using standard JSONPath expressions. For information about this, see Mapping data to Cloud Cruiser.

Filter records when collecting customers

When importing customer records using CustomerCCRecordCollector, you can now use a standard filter property to specify which CC Records should be imported.

Transform processor enhancements

The following transform processors are added or enhanced in this release. For information about these processors, see the JavaBean Reference documentation at <install_dir>/docs/api/batch/com/cloudcruiser/batch/transform/package-frame.html.


There are two enhancements in this release:

  • Added support for audit events. These are control events that report resources observed within some time period. In the case of Nova, it is the audit period which may be configure to hourly or daily. This is different from previous control data that represented a point in time where the resources are known to exist.
  • The new boolean properties syncInsertEnabled and syncDeleteEnabled tell the processor whether to trust the control feed over the records being processed. When ​syncInsertEnabled is true, the processor creates a new CC Record when a record exists in the control feed without a corresponding record in the processed set. When syncDeleteEnabled​ is true, the processor deletes a CC Record when no corresponding record exists in the control feed.


The new property defaultToSourceOnException controls what happens when no match is found and exception processing is off. When true, the value of the source identifier is written to the target identifier, the previous behavior of the processor. When false, the processor does nothing to the record.


This new processor drops all identifiers except those specified.


This processor now creates an empty output file instead of no output file when no records are diverted.


This new processor subtracts one second from the end time. This is needed when data contains an exclusive end time because we expect inclusive end times.


This new processor modifies a record to have only an end time by dropping the start time. If no end time exists, the start time is copied to the end time before being dropped.


This new processor modifies a record to have only a start time by dropping the end time. If no start time exists, the end time is copied to the start time before being dropped.

Tasklet enhancements

The following batch tasklets are enhanced in this release.

Transform exception files are reset for each run

The exception file for a transform step using CCRecordTransformTasklet is now initialized before record processing begins. This ensures exceptions from a previous run are cleared out if the job is executed again for same date.

Sort uses start time by default

When CCRecordSortTasklet compares timestamps to sort records where all other identifiers match, where both start and end times exist the comparison now uses the start time by default. Previously the end time was the default. You can compare end times by setting the new preferEndTime property to true.

This change was to resolve issues with event correlation because true chronological order is expected there. For information about CCRecordSortTasklet, see the JavaBean Reference documentation at <install_dir>/docs/api/batch/com/cloudcruiser/batch/CCRecordSortTasklet.html.

Aggregation can combine records with distinct resource values

The defaultFunction property of CCRecordAggregationTasklet now accepts a value of DISTINCT. This function combines only records where all resource values match. These values are untouched: aggregation only merges usage periods and mutable identifiers. You can also use DISTINCT when using AggregateResource to specify the aggregation function for an individual resource.

For information about CCRecordAggregationTasklet, see the JavaBean Reference documentation at <install_dir>/docs/api/batch/com/cloudcruiser/batch/CCRecordAggregationTasklet.html.

Job Monitoring timestamps more precise

All timestamps in the Job Monitoring window, including log messages, now include hours, minutes, and seconds.

Run reports via REST API with job-specific parameters

The REST API method for running a report has a new element extraParameters that enables you to pass job-specific parameters to the report engine.

For information about using this element in a REST API call, see Run a report. For information about job-specific parameters, see "Report-specific parameters" in Report properties.

Bugs fixed

The following bugs have been fixed since the Cloud Cruiser 3.4 release:



Bug ID

The Microsoft Azure collector failed with the error There is no data for select date to download when the list of available Azure usage reports included one whose date range only listed the starting and ending month and year, even if a report existed for the selection date and with a correctly formatted date range.

Microsoft Azure displays this shorter date format on some usage reports requested during April 2014, regardless of the date range requested. When the collector now encounters such a report, it ignores the report (it needs exact dates) and continues scanning the list of available reports to find another one matching the selection date for the current run. If the dates for which you want to collect data are in a report listed with short-format dates, you must request a new report for the same date range.


The Microsoft Azure collector failed with the error IndexOutOfBoundsException when it requested a usage report for a date for which no data was available and that request produced an entry on the Download Usage Data page that said No data without a downloadable link.

The collection job now completes without failing.


The Resource Invoice and Resource Invoice Summary reports displayed incorrect account IDs when run using an Account Structure other than the default structure.

This fix was released in version 3.4 but was not applied when upgrading an existing installation. Upgrading to version 3.5 does apply the fix.

3693, 3714
The Profit and Loss By Account report showed an incorrect GM% value of -100% when the Revenue value was less than 1. None
The Windows Azure Pack Collector failed when the hostname of a data source included the string usage. 3805
The sample job for the Windows Azure Pack Collector had a low exception limit for records with a SubscriptionId that did not exist in Azure Pack, causing the job to fail often. This limit is now raised. None
After attempting to save a customer, transaction, discount, or surcharge with certain missing or incorrect information, the Save and Cancel buttons did not reappear even after editing the object to correct the error. 3354

System requirements


​The following are the minimum hardware and software requirements for Cloud Cruiser and its components.

HPE recommends that you install Cloud Cruiser, Cloud Cruiser Analytics Server, and your database server on separate computers. These system requirements apply to that architecture.

Cloud Cruiser computer

You should also install HPE Consumption Analytics Portal Desktop on this computer.


  • 2 GHz or faster multi-core processor
  • 4 GB or more of system memory
  • 2 GB of storage

Operating system

You must use the 64-bit version of one of the following operating systems:

  • Microsoft Windows Server 2008
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2012 R2
  • Linux with a v2.6 or later kernel

The Server Core installation option of Windows is not supported. The Cloud Cruiser installer requires a graphical user interface and cannot be run within a command window.

Java platform

The 64-bit version of Java Standard Edition 7 (JDK or JRE) is required. Version 8 is not supported.

You can download Java at The navigation of this site changes often, so you might need to look carefully to find version 7 in 64 bits.

Database server computer

A database server is not included with the Cloud Cruiser installation. You must provide one of the following database servers:

  • Microsoft SQL Server 2008 or 2012
    ​The Express edition is not supported. Its limitations will result in unacceptable performance, even in small installations.
  • Oracle 10g or 11g

​​For hardware and operating system requirements for this computer, see the documentation for your database server. Storage needs will grow as Cloud Cruiser accumulates data over time.

Client computers

One of the following browsers:

  • Microsoft Internet Explorer (IE) 10 or newer
    Although the product works on 32-bit versions of IE, Cloud Cruiser strongly recommends that you use the 64-bit version of IE for better performance.
  • Mozilla Firefox
  • Google Chrome

As of the last update to this article, Cloud Cruiser has been tested with Firefox 32 and Chrome 37, and we continue to test with new, automated version updates of these browsers. The application should continue to function with such versions. However, some issues could arise that can only be resolved with subsequent patches to Cloud Cruiser or by reverting the browser update.

Programming documentation

The following programming documentation for Cloud Cruiser is provided in the <install_dir>/docs directory:

  • JavaBean Reference (HTML) at <install_dir>/docs/api/batch
    The documentation for the Cloud Cruiser JavaBean library for batch jobs in Javadoc format. To get started, open index.html.
    Beans are organized into packages such as collection, transform, and filter. Spring Batch XML examples are included throughout.
  • REST API Reference (HTML) at ​<install_dir>/docs/api/rest
    The documentation for the Cloud Cruiser REST API in Javadoc format. To get started, open index.html.
    Methods are organized into interfaces for areas of functionality such as budget alerts, reports, and rate plans.

Last modified



This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP