 |
Consumption Analytics Documentation |
|
Consumption Analytics Documentation |
This section contains the cumulative release notes for HPE Consumption Analytics Portal version 3.6.x. The current release is version 3.6.8.
All documentation articles updated for this release have the tag version_3.6. List these articles.
The following features are new or enhanced in HPE Consumption Analytics Portal version 3.6.
You can now update your Amazon Web Services (AWS) usage and charge records with more accurate data after the end of a month. The final invoice from AWS, available several days after the end of the month, provides updated usage totals that are not in the hourly reports you collect daily. Run the AWSCollector against the current date on or after the 10th of a month with the new endOfMonthMode property set to true to capture data from a final invoice.
The OpenStack Ceilometer collector interacts with both the Ceilometer and Keystone APIs of OpenStack. Each of these has multiple endpoints available: a public URL, an internal URL, and an admin URL. In this release, you can specify which of these URLs the collector uses, allowing it to work in an environment where access to certain endpoints is restricted.
For information, see Creating a data source.
The new transformation processor ApplyIdentifierExpirations removes expired identifiers from input records by matching those records against a separate CCR file of expiration events and splitting them at the time an identifier "expired." Expiration represents a disassociation of two objects. This allows you to correctly represent the state of one object after it was disassociated from another.
The new transformation processor CreateIdentifiersFromIdentifierJSON parses an identifier value collected in JSON format and extracts name/value pairs as new identifiers. You can specify how many levels the processor traverses in the JSON hierarchy and several options for naming the new identifiers.
The following enhancements to the ConvertEventsToAllocations processor are made in this release.
You can now perform transformation on records that are to be written to the next day start feed by using the new postProcessors property. This allows you to add a list of transformation processors. These processors are run against records just before writing them to the next day start feed. They are not run against records in the main flow.
Sometimes information is provided as part of a create event for an object, but not as part of later update or delete events for the object. To retain this context, use the new stickyIdentifiers property. This lets you specify a list of identifiers that roll forward, even if empty. The last value encountered, based on sort order, is used.
An audit event is a control feed record that has both start and end times, providing more precision than a regular control feed record. The times do not represent actual times for charging, but rather a window during which an object was observed to exist at some point.
Use the syncDeleteEnabled property to trust control feeds to delete a record, the syncInsertEnabled property to trust control feeds to create a record, and originCondition to specify whether a record with only a start time represents the creation of an object that has an audit record or the modification of that object.
In version 3.6.2, the Microsoft Azure Collector now collects using the new Azure API instead of imitating a live user of the Azure Enterprise Portal website. This makes the collector more reliable, as unforeseen changes to the website will no longer affect the collector.
The following features are new or enhanced in HPE Consumption Analytics Portal version 3.6.3.
RoundingError line of an Amazon Web Services (AWS) billing report, so the charges that were lost to mathematical calculations are now captured by HPE Consumption Analytics Portal. These charges are collected as a separate resource.ConvertIdentifierToUsageEnd processor sets the usage end date and time to the value of a specified identifier.ConvertIdentifierToUsageStart processor sets the usage start date and time to the value of a specified identifier.UsageEndDate filter lets you restrict a transformation processor based on the end date in each record. When the usage end date matches a value you provide, the filter returns true.You can now use the ImportNewResources transformation processor now has a hiddenFlag property. When set to true, the resources imported by the processor are hidden from reports. This was already available as a record-level option when importing resources via the ccimport utility.
In version 3.6.4, the HP Cloud Service Automation (CSA) Collector collects a filtered set of subscriptions instead of collecting all subscriptions and then using transformation to filter them. This results in faster performance.
The following features are new or enhanced in HPE Consumption Analytics Portal version 3.6.5.
You can now specify whether to authenticate a particular user with HPE Consumption Analytics Portal's internal authentication or the external authentication method you're using. When using LDAP or SSO authentication (for information, see Configuring authentication), the Users page includes an Authentication Type option that you can set to either Internal or your external method.
You can now specify a timeout value for the HP Cloud Service Automation (CSA) 3.x Collector, which previously timed out after one minute. You do this in an HP CSA data source, which now includes a timeout property. The timeout is specified in seconds with a default of 60.
HPE Consumption Analytics Portal has been updated to include Tomcat 7.0.59, which provides enhanced security from previous Tomcat versions.
The following bugs were fixed in the HPE Consumption Analytics Portal 3.6 release:
| Description | Bug ID |
|---|---|
| When the This behavior is now optional with the processor's new | 4371 |
| When running a report via the REST API, a user had access to all financial records in the HPE Consumption Analytics Portal database. Group-level security was not applied. | None |
The following bugs were fixed in the HPE Consumption Analytics Portal 3.6.2 release:
| Description | Bug ID |
|---|---|
| The HP Cloud Service Automation (CSA) Collector failed when a request to the CSA API returned a minor error such as an HTTP 400 error. Minor API request errors are now handled as exceptions. | 4582 |
| When using the HP CSA Collector with CSA 4, the collector failed when collecting more than 800 rows. | 4637 |
| The Amazon Web Services (AWS) Collector did not account for the difference between UTC and the time zone of the HPE Consumption Analytics Portal server, resulting in daily collections for a period that was offset by that number of hours. | 4642 |
The following bugs were fixed in the HPE Consumption Analytics Portal 3.6.3 release:
| Description | Bug ID |
|---|---|
Identifier values that contained the double-quote character (") were parsed incorrectly. | 4426 |
The following bugs were fixed in the HPE Consumption Analytics Portal 3.6.5 release:
| Description | Bug ID |
|---|---|
| The HP Cloud Service Automation Collector did not collect subscriptions that were deleted only a few hours after being created. | 4805 |
| Some resource values were multiplied by 10,000. | 4673 |
The following are the minimum hardware and software requirements for HPE Consumption Analytics Portal and its components.
HPE recommends that you install HPE Consumption Analytics Portal, HPE Consumption Analytics Portal Analytics Server, and your database server on separate computers. These system requirements apply to that architecture.
A database server is not included with the Cloud Cruiser installation. You must provide one of the following database servers:
For hardware and operating system requirements for this computer, see the documentation for your database server. Storage needs will grow as HPE Consumption Analytics Portal accumulates data over time.
One of the following browsers:
As of the last update to this article, HPE Consumption Analytics Portal 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.