This section contains the cumulative release notes for Cloud Cruiser version 4.2.x. The current release is version 4.2.11.
All documentation articles updated for this release have the tag version_4.2. List these articles.
Cloud Cruiser 4.2.11 fixes the following bugs, which include a critical issue with Azure data collection:
Java Error running report: java.lang.Boolean cannot be cast to java.lang.Integer
The following features are new or enhanced in Cloud Cruiser version 4.2.10.
Cloud Cruiser has enhanced its ability to collect data from Microsoft Azure. The changes include an enhanced Microsoft Azure data source, and three new collectors for usage, diagnostics metrics, services, and rates.
The new Microsoft Azure data source connects to your Microsoft Azure Active Directory client application, enabling you to collect data for the devices, services, and rates in one or more Active Directory accounts, and for any of the subscriptions in those accounts. For more information, see Creating Microsoft Azure data sources.
The data source named Microsoft Azure in previous Cloud Cruiser 4.x releases has been renamed Microsoft Azure EA Billing in version 4.2.10. The renamed data source functions exactly as it did in previous previous versions. The only change is its name.
The Microsoft Azure Tags data source is deprecated in Cloud Cruiser 4.2.10. To collect Azure tags, use the new Microsoft Azure data source in conjunction with the Microsoft Azure Tags collector.
Cloud Cruiser has added three new collectors to enhance your ability to collect Microsoft Azure data. For more information about these collectors, see Creating Microsoft Azure collections.
The collector named Microsoft Azure in Cloud Cruiser versions 4.1.3 to 4.2.9 has been renamed Microsoft Azure EA Billing in version 4.2.10. The renamed collector functions exactly as it did in previous versions. The only change is its name.
See Bugs fixed in 4.2.10 for details about the bugs fixed in version 4.2.10.
The following features are new or enhanced in Cloud Cruiser version 4.2.9.
Cloud Cruiser now supports data collection for Amazon CloudWatch metrics, which enable you to monitor your Amazon Web Services (AWS) resources and the applications you run on AWS. For more information about configuring collection of Amazon CloudWatch data, see Amazon CloudWatch.
You can now send usage data through a proxy server as part of the Post Usage ETL step. When configuring a Post Usage step, you can define the following additional fields:
See Bugs fixed in 4.2.9 for details about the bugs fixed in version 4.2.9.
The following features are new or enhanced in Cloud Cruiser version 4.2.8.
Cloud Cruiser now includes an option to toggle whether charge jobs run. This enables you to test your Cloud Cruiser implementation as you are working without generating charge records that would otherwise need to be removed each time you run an ETL workbook.
To disable or enable charge jobs
Yesif you want charge jobs enabled, or
Noif you want charge jobs disabled.
You can now include tags as metadata in your rate plans when importing a rate plan using the
ccimport utility or the REST API. For more information about importing rate plans, see CCIMPORT and CCEXPORT reference and Import rate plans.
Prior to version 4.2.8, the Cloud Cruiser API did not authenticate users in SSO configurations. This could cause errors when displaying reports, for example. The API now supports authentication through SSO. For more information about the Cloud Cruiser API, see About the API. For more information about configuring SSO authentication in Cloud Cruiser, see SSO authentiction.
See Bugs fixed in 4.2.8 for details about the bugs fixed in version 4.2.8.
The following features are new or enhanced in Cloud Cruiser version 4.2.7.
Cloud Cruiser now supports the collection of Amazon Marketplace data through the standard Amazon Web Services collector. When configuring your collector, you now have a choice between standard billing reports or Amazon Marketplace data. For more information about how to configure the collection of AWS data, see Amazon Web Services.
Cloud Cruiser can now collect Microsoft Azure tags along with your Azure data. To support this optional capability, Cloud Cruiser now includes a Microsoft Azure Tags workbook template that includes the flows necessary to collect tag data. For more information, see Collecting Microsoft Azure tags and data.
Microsoft changed the following column header names in their Usage Detail data, effective for data dated August 1, 2015 and later:
Cloud Cruiser's Microsoft Azure workbook templates have been updated to accommodate those changes, and can now collect data using both old and new headers. If you are collecting Microsoft Azure data in a version of Cloud Cruiser earlier than 4.2.7, contact Support for assistance.
The Join Dataset workbook step enables you to join data from a selected dataset to the current worksheet based on key dimensions you specify. You can specify which dimensions and measures are joined, and whether data in the worksheet is overwritten or retained if there is an exact match of data. For more information, see Step types.
Whether exporting reports using the Cloud Cruiser API or the Export option in the Cloud Cruiser Portal, exports to CSV and XLS files are presented in a tabular format. Prior to this enhancement, CSV and XLS report exports made through the Cloud Cruiser API were presented in a more graphical format, similar to the reports displayed within the Cloud Cruiser Portal.
See Bugs fixed in 4.2.7 for details about the bugs fixed in version 4.2.7.
The following features are new or enhanced in Cloud Cruiser version 4.2.6.
You can now apply an Average to Date proration type for allocated services, smoothing usage over a period of time. If your service has a Monthly charge interval and you are collecting daily usage data for that service, the daily usage amounts are summed for monthly charging. Prior to 4.2.6, this could result in usage for a rate-plan tier to exceed the maximum amount defined for that tier if an individual day's usage was above the maximum for that tier. With Average to Date proration introduced in 4.2.6, usage is smoothed to allow the total usage for a period to be properly allocated within the tiers defined for a service. For more information, see Creating services.
Prior to 4.2.6, you could specify Sticky Tiers and Final Tier rate types for a service. As of 4.2.6 these types have been expanded, enabling you to use metered tiering for allocated services. When you select a metered rate type for an allocated service, time-based units are used to determine the tiers reached. For example if you have a service for a 50GB disk, and you charge monthly for that service, the single-day time-based unit for that service in a 30-day month is 1.67 GB-months (50/30=1.67). As usage grows, charging might change as different rates are applied by tiers. For more information, see Managing rate plans.
Prior to 4.6.2, combining account levels and minimum commitments for a tiered service rate sometimes created a scenario in which customers at an account level were charged for service usage, while customers at a child account level were also charged for the same usage. As of 4.2.6, if you define an Account Level and a Min Commit for a tiered service rate, the Min Commit value is applicable only to accounts with customers defined. For example, say your account structure is Business Unit, Department, and Region, and you have set an Account Level of Department for the tiered service rate. For usage at the Region level to be rolled up to the Department level, you must have at least one customer defined at the Department level. For more information, see Managing rate plans and Creating customers.
See Bugs fixed in 4.2.6 for details about the bugs fixed in version 4.2.6.
You can now add customized text to the Cloud Cruiser Sign In page, just below the Password field. For example, you might add text that alerts users that by signing in they agree to your terms of service, and you can include a link to your terms of service as part of that text.
For more information, see Rebranding the user interface.
The following features are new or enhanced in Cloud Cruiser version 220.127.116.11.
The Microsoft Windows Azure Pack workbook template has been updated to make it easier for you to collect Windows Azure Pack usage data and associate that data with a rate plan for pricing. The changes include the publishing of
mysqlserver Windows Azure Pack data.
Database schemas to support the updated template are now installed as part of a fresh Cloud Cruiser installation. However, if you are upgrading from an earlier version of Cloud Cruiser you must first import the
<install_dir>\schemas\WindowsAzurePack_schema.csv file from the Data > Setup > Schema Management page in Cloud Cruiser.
Before using the updated template you must complete the following actions:
WindowsAzurePack_services.csvfile from the
WindowsAzurePack_rateplan.csvfile from the
See Bugs fixed in 4.2.4 for details about the bugs fixed in version 4.2.4.
If you want to use Cloud Cruiser to connect to an Amazon Web Services or Microsoft Azure data source through a proxy server, you can now do so by specifying proxy information when creating your data source in Cloud Cruiser. For more information about creating data sources, see Data sources.
In version 4.2.2, the ETL workbook and schema templates for the Microsoft Azure Collector now include the Department Name and Cost Center fields.
To add these fields to an Azure collection from a previous version
The following features are new or enhanced in Cloud Cruiser version 18.104.22.168.
The Microsoft System Center Collector is now available, enabling you to collect both Service Manager and Operations Manager components from System Center 2012 SP1.
Cloud Cruiser 4.2 requires Java 8 and does not support Java 7. This is a change from Cloud Cruiser 4.0.x and 4.1.x, which require Java 7 and do not support Java 8. For more detail on this requirement for version 4.2, see the section System requirements.
If you are upgrading to version 4.2, in addition to installing Java 8 you must change the value of the
JAVA_HOME environment variable to the location where Java 8 is installed. For instructions on setting this variable, see Configuring Java.
Oracle version 11g and later is now supported as the database server for Cloud Cruiser 4. Oracle was already supported on version 3. Complete system requirements for version 4.1 are in the section System requirements.
Cloud Cruiser offers extensions to Microsoft Windows Azure Pack that allow Cloud Cruiser charges to display in the Windows Azure Pack management portals for administrators and tenants. These extensions were compatible with only Cloud Cruiser 3 because they leverage the REST API, which changed in Cloud Cruiser 4. As of February 10, 2015 the new version 22.214.171.124 of these extensions is compatible with Cloud Cruiser 4. This new version also includes the ability to use a calendar widget when specifying a custom date range for reports.
To obtain version 126.96.36.199 of the Windows Azure Pack extensions, see the procedure in Enabling Windows Azure Pack to display Cloud Cruiser data.
Version 188.8.131.52 requires the security update for ASP.NET MVC 4.0 released on October 14, 2014. For more information about this update, see https://support.microsoft.<wbr/>com/kb/2993928/en-us.
The user interface for scheduling the running of ETL collections, ETL flows, and XML jobs is now easier to use. It also enables you to schedule multiple components to run sequentially and to easily view a list of completed runs for each schedule.
The Scheduling page is in the same location as before: Data > Processing > Scheduling.
You can now create an effective date range for a rate plan that includes an end date as well as a start date. This allows you to give special rates to a set of customers for a limited time, after which they revert to the Default rate plan.
Previously, a Post Usage step in an ETL workbook wrote the usage data to a file named for the date when the post occurred, which did not always match the select date of the data being posted. You can now optionally specify a select date in your Post Usage step to control the date used in the name of the file written by the step.
Versions 4.1.0 to 4.1.2 included two collectors for Microsoft Azure, one that collected by logging into the Azure Enterprise Portal as a user and a newer one that collected via the Azure API. In November 2014 Microsoft made changes to the Azure Enterprise Portal that prevent the older collector from working.
Because the API-based collector can more reliably collect recent data from Azure, Cloud Cruiser will no longer maintain the older collector. Version 4.1.3 includes only the API-based Microsoft Azure collector.
As part of a bug fix, two changes were made regarding time zones.
Usage start and end times are now displayed in the workbook time zone. They previously were displayed in UTC. This change allows a full day's usage in a workbook with a time zone other than UTC to appear as 0:00:00 to 23:59:59 instead of spanning two days.
After upgrading from a previous release to version 4.2, do not be alarmed by the different start and end times you see when viewing sample data in a worksheet. This change does not affect the underlying data in CCR files, only the worksheet view.
When a collection or flow is run, either from the Run button in the ribbon or from a schedule, the run (in batch XML terms, the process) now uses the workbook time zone. Previously the run used the Cloud Cruiser system time zone. Workbooks with a time zone that is different from the system time zone will now produce different usage start and end times in collected CC Records.
After upgrading from a previous 4.x release to version 4.2, to make the usage start and end times in new collected data consistent with those in previously collected data you must set workbook time zones to match the system time zone.
The following important bugs are open in the Cloud Cruiser 4.2 release:
When a Standard Invoice report contains a discount or surcharge, that line includes a drill-down link. This link should not appear because there is no usage information into which to drill down for a discount or surcharge, and the link returns error messages.
The Cloud Cruiser service has a default Log On As setting of local service. If you change this setting and then upgrade Cloud Cruiser, the Log On As setting reverts to its default setting.
To work around this issue, change the Log On As setting after upgrading Cloud Cruiser.
The following bugs are fixed in the Cloud Cruiser 4.2.11 release:
|Key format updates in Azure produced a 404 error when Cloud Cruiser attempted to connect to Azure.||MAINT-253|
|Clicking Preview Invoice in a What-If scenario produced the following error: ||MAINT-214|
The following bugs are fixed in the Cloud Cruiser 4.2.10 release:
|When viewing the Cloud Cruiser portal in the Microsoft Edge browser, dialog boxes had a blue background, making buttons and text more difficult to read.||MAINT-220|
|Running a Publish to Customer workflow step caused duplicate customer records to be created in the Cloud Cruiser database.||MAINT-205|
The following bugs are fixed in the Cloud Cruiser 4.2.9 release:
|On the Financial > Customers page, sorting customers by Description actually sorted customers by Account ID.||MAINT-151|
|When using a Min Commit value for a service with the Basic Rate Type, Cloud Cruiser generated two charge records for the service.||MAINT-142|
Windows Azure Pack data was not collected completely unless the workbook was set to the UTC time zone.
|While publishing data, opening several reports in rapid succession caused Cloud Cruiser to become unresponsive.||MAINT-133|
Due to a lower-than-required version of Joda, Amazon Web Services data collection produced the following error:
|After creating a new level in the account structure and then creating a customer assigned to that level, the new customer did not appear in the list of Customers when the list was filtered to show only that Account Level.||MAINT-93|
|Using the REST API to update customer records failed.||MAINT-79|
The following bugs are fixed in the Cloud Cruiser 4.2.8 release:
When using SSO, running a report that includes a logo fails with the following error:
For any specific API table, you could have only one update request active at a time. Concurrent updates returned an Internal Service Error on the client side, and a Transaction Deadlocked error on the server.
|You could not use the REST API to update a customer record. Cloud Cruiser returned a ||No ID|
|Cloud Cruiser processed credits to Amazon Web Services accounts multiple times, when each credit should have been processed once.||No ID|
The following bugs are fixed in the Cloud Cruiser 4.2.7 release:
|When exporting reports to CSV, the account ID was shown as NULL if the Account Level selected was last in the list of accounts.||5277|
|Running the ||5257|
|Cloud Cruiser failed to connect to Cisco IAC version 4.1, returning an unauthorized access error.||5250|
|With SSO authentication, users created locally in Cloud Cruiser (not imported user accounts), were unable to log in.|| |
|With SSO authentication, users could not open workbooks.||5244|
|API documentation for Lookups was not current for changes made in the API after version 4.1.||5242|
|When commas were included in report parameters, Cloud Cruiser was unable to export report results to CSV or XLS formats.||5232|
|When exporting CSV and XLS report files, Cloud Cruiser named the file "export" instead of the actual report name.||3321|
|The Export menu for standard reports included "2007" in the Microsoft Word and Microsoft Excel export options.||3320|
|Report exports to XLS formats turned numeric values into text, preventing calculations in spreadsheets.||985|
|Numbers in drill-down reports were shown as letters in Excel exports of the report.||390|
The following bugs are fixed in the Cloud Cruiser 4.2.6 release:
|In What-If scenarios, the Account Level column was in the wrong location, contained incorrect data, and could not be edited.||5252|
|Ranges in lookup tables were not being read as strings, resulting in incorrect and failed matches for Target IDs.||5251|
For services that use a tiered rate plan and have a Min Commit value set, Cloud Cruiser calculated usage for each tier incorrectly, which could result in displayed usage for a tier above the maximum allowed for that tier.
The following bugs are fixed in the Cloud Cruiser 184.108.40.206 release:
|A multithreading issue caused random services to be charged at a highly-inflated cost.||5229|
|An inaccurate assignment of Windows Azure Pack ||5225|
|In custom reports, the Accounting Year field showed only 2015 as a value, even if data for other years was available. Attempting to change the year produced an error with the following message: "Internal client error - Browser refresh may be necessary"||5224|
|In custom reports, the Accounting Year field passed a ||5223|
If the domain name of your Windows Azure Pack data source endpoint included the word "usage" you received a "Failed to parse JSON response" error when testing your endpoint connection.
The following bugs are fixed in the Cloud Cruiser 220.127.116.11 release:
Some ETL workbooks became corrupted and would not open, instead displaying the error message
Upon opening such a workbook with version 4.2 for the first time, the displayed sample data might be out of sync. To fix this, manually refresh sample data.
The Default Charge Job fails when a service quantity has more than 13 digits.
The Default Charge Job sometimes failed for Amazon Web Services (AWS) data. This was due to a time zone setting that caused the load to contain more than one accounting date.
The fix for this bug causes the start and end times to shift when viewing AWS data in an ETL workbook, but the timestamps in the Cloud Cruiser database remain unchanged. For more information, see the section Time zone display and behavior changed.
|Manually running the Default Charge Job for a range of dates in the Advanced Job Maintenance window sometimes failed to charge some usage. The job run results for some of the dates in the range would include the message ||5013|
|When the Default Charge Job finds usage against a service for two customers, only one of those customers is associated to a rate plan, and the Use Default Rate Plan if Missing Rate configuration option is set to No, no usage for that service is charged. The usage for the customer associated to a rate plan should have been charged.||5172|
The Microsoft Azure collector stopped working in November 2014.
This was due to changes Microsoft made to the Azure Enterprise Portal website, and did not affect the Microsoft Azure (API) collector. Now Cloud Cruiser includes only the API-based collector.
|When the Default Charge Job processed a recurring transaction, it failed with a null pointer exception.||Support ticket 1433|
|When you processed a transaction for a service that has no rates in the customer's rate plan, and the configuration option Use Default Rate Plan If Missing Rate is enabled, the Default rate plan was not used. Instead the Default Charge Job failed with the message ||5076 (Support ticket 1434)|
|The Windows Azure Pack collector was unable to successfully process usage under subscription ID ||5078|
|A Cisco IAC collection did not work if the Subscription Filter option was blank. There was no way to make the collection retrieve all service item types.||5138|
|The Amazon Web Services collector produced usage start and end times in the wrong time zone. This caused Publish steps to fail.||5055|
|The Rename Measures from Lookup transformation processor would proceed to rename a source measure if its target name was the same as an existing measure, resulting in duplicates.||2700|
|When you added one or more levels at the top of your account structure, user groups with Customers Allowed set to All were not able to see data for customers or accounts at the new levels.||4905|
|When working in an ETL workbook that has an Amazon Web Services collection that retrieves a large dataset, capturing a new set of sample data caused your browser to freeze. This is because the collection ignored the Data Sample Limit you set, instead capturing all possible data for the workbook's select date.||5033|
|For data sources that execute a command, the Timeout parameter was specified in milliseconds instead of seconds.||4844|
|When importing services and rates together with ||4866|
|After reordering levels in your account structure, in some cases standard reports displayed account IDs rather than customer descriptions.||5029|
There was no way to import custom descriptions for individual rates when importing rate plans or importing services and rates together.
You can now specify such descriptions in a
If you used the REST API to try to delete a rate plan that had been used to charge for any usage, you received a long, cryptic error message. That message now reads:
If you upgraded from version 4.0.x to version 4.1.1, two standard reports would not run:
|In a Standard Invoice report, if you clicked a drill-down link for a usage number or service group, you received a blank window.||5119|
|In a Standard Invoice report, units for Microsoft Azure services were incorrect. You had to drill down into those units to see the correct amounts.||5009|
|The Service Invoice Summary report did not display charges from a transaction against a service with Sticky Tier pricing. Also, when a units transaction was charged against a service with a Sticky Tiers rate, the ||5168, 5169|
|In the What-If page, the Preview Invoice tab did not show an invoice for the selected model. It displayed the error message ||4869|
|If you edited the XML job for a workbook component and added only one of the ||3419|
|The first time you viewed a customer in the Customers page, inactive and processed transactions were visible without clicking Show Inactive or Show Processed.||5026|
|Cloud Cruiser continued to use the same cached database password for communicating with Cloud Cruiser Analytics Server even after you changed the password in the Configuration area of the Cloud Cruiser Portal, effectively requiring you to restart the application server to complete a password change.||5189|
|When specifying credentials for Cloud Cruiser Analytics in the Configuration area of the Cloud Cruiser Portal, after you got a successful result by clicking Test Connection the test would never fail again no matter what changes you made in the window.||5182|
You should also install Cloud Cruiser Analytics Desktop on this computer.
The 64-bit version of Java Standard Edition 8 (JDK or JRE) is required. Versions earlier than 8 are not supported.
You can download Java at http://www.java.com/getjava. The navigation of this site changes often, so you might need to look carefully to find version 8 in 64 bits.
One of the following operating systems:
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 Cloud Cruiser accumulates data over time.
One of the following browsers:
As of the last update to this article, Cloud Cruiser has been tested with Firefox 32 and Chrome 44, 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.
The documentation for Cloud Cruiser 4.x is located at Cloud Cruiser 4. At this time, very little documentation is available, and we are continuously adding to it to fully document the release.
In addition to the documentation available on this site, version 4 has more help within the Cloud Cruiser Portal. This includes help for windows, dialogs, and the functions and parameters in Data > Workbooks.