This topic contains the cumulative release notes for Cloud Cruiser 16. For complete documentation about configuring and using Cloud Cruiser, see Cloud Cruiser 16.
Changes in recent releases
This section lists the enhancements and bug fixes in recent releases of Cloud Cruiser. For information about older releases, see the Archive of Cloud Cruiser 16 release notes.
March 21, 2017
On March 21, Cloud Cruiser released version 1.40.5, which includes the following bug fixes:
- Fixed bug: When you clicked the DEMO DATA MODE button, the USE DATA MODE and ADD NEW COLLECTION buttons were still active and clicks generated events.
- Fixed bug: When a new user was created, and that user tried to activate the account, they had to log out and log in again to see the 'Sample Data' banner.
- Fixed bug: When a report returns zero records, PDF generation failed with a "java.lang.NullPointerException" if the report had a group configured, or if no group was configured if failed with "java.io.IOException: javax.xml.transform.TransformerException: org.apache.fop.fo.ValidationException: "fo:table-body" is missing child elements. Required content model: marker* (table-row+|table-cell+) (No context info available)".
March 14, 2017
On March 14, 2017 Cloud Cruiser updated version 1.40.2, which includes the following bug fix:
- Fixed bug: Resetting a forgotten password did not work when the customer typed in a mixed case email address.
March 8, 2017
On March 8, 2017 Cloud Cruiser released version 1.40.2, which includes the following enhancements and bug fixes:
- Distributed reports can now be sent to any active user, regardless of sharing status.
- Fixed bug: On a mobile device, Single Sign On was not available.
- Fixed bug: When creating a Microsoft Azure collection during the first few days of a month, in some cases you received an Invalid Credentials error and could not save the collection.
- Fixed bug: Some newly created users did not receive reports that were set to be distributed to them.
March 1, 2017
On March 1, 2017 Cloud Cruiser released version 1.39.14, which fixes a bug that caused long numbers to be truncated in some charts.
February 27, 2017
On February 27, 2017 Cloud Cruiser released version 1.39.13, which includes the following enhancements and bug fixes:
- Cloud Cruiser now shows you the status of background processing initiated by a user. This includes recollecting data for a collection and reprocessing data, which can be triggered by running SmartTags rules for a collection or by changing currencies. You see this status by clicking the icon at the top of the window, which opens the Active Processes dialog. All users in your account see this icon, helping them understand that the reports and charts they are viewing might have inaccurate values durng the processing.
- You can now delete Fixed fields as well as Custom fields. This is particularly useful if you used Demo Mode to try the product and no longer want to see the Fixed tag fields from the Demo Mode dataset.
- When deleting a field, more potential references to that field are checked, preventing you from breaking a report or other content you've created by deleting the field.
- Fixed bug: Some budgets displayed email notification thresholds in the wrong order
- Fixed bug: For budgets with targets per field value, email notifications sometimes included a row for the total budget when that target shouldn't have been included.
- Fixed bug: When creating a new What-If model, you sometimes received the error message
Error generating price list.
- Fixed bug: If you created a Custom field with the same name as a Fixed field from an AWS collection, values from one were placed in the other.
February 6, 2017
On February 6, 2017 Cloud Cruiser released version 1.38.8, which enhances the product to notify users to expect temporary fluctuations in their analytics while Cloud Cruiser performs the following types of processing:
- When the user changes the Display Currency, causing a conversion of Cost and Rate values from one currency to another
- When the user leaves Demo Mode, causing the deletion of sample data and the collection of their own data
February 2, 2017
On February 2, 2017 Cloud Cruiser released version 126.96.36.199, which includes the following bug fixes:
- Fixed bug: One Azure collection was populating the wrong field with collected data
- Fixed bug: One Azure collection did not populate the Resource Name field correctly
- Fixed bug: Budget notifications for projected violations were not working as expected. Budgets set for weekly notifications were sending emails more frequently, whenever the projected date of violation changed. Budgets set for daily notifications did not send emails at all.
January 26, 2017
On January 26, 2017 Cloud Cruiser released version 1.36.3, which fixed a bug with onboarding new customers. Previously, if a user logged out of Cloud Cruiser without having created their first collection or entered Demo Mode, they would not be forced to finish that onboarding step the next time they logged in. This allowed users to navigate throughout a product that displayed no data.
January 24, 2017
On January 24, 2017 Cloud Cruiser released version 1.35.2, which includes the following enhancements and bug fixes:
- You can now try Cloud Cruiser in Demo Mode. This provides sample AWS and Azure data so that you can fully experience the product without access to the credentials that are required to collect your own cloud data.
- Fixed bug: For Microsoft Azure collections, the Resource Group field was empty.
- Fixed bug: If two or more SmartTags rules were invalidated by a change to a lookup they reference, you could not save edits to them.
- Fixed bug: When a budget included a filter, the filter did not affect the budget's Historical Performance chart.
January 19, 2017
On January 19, 2017 Cloud Cruiser released version 1.34.20, which includes the following enhancements and bug fixes:
- Support for non-US currency and locales. Cloud Cruiser can convert cloud charges from any source currency to your preferred display currency and format it for your preferred locale. For more information, see Currency and locale.
- The new Outlier rule template for Insights lets you detect the "bad actors" in your organization who spend or use more than others. For more information, see Rule templates.
- Support for Amazon Web Services' new London region.
- In What-If, when you click to edit a VM the service catalog now scrolls to show its current type.
- Insights now displays units (MB, $, etc.) in more places to help you understand the meaning of numbers.
- Fixed bug: When you edited a lookup and scrolled up or down in the table, edits were applied to the wrong cells.
- Fixed bug: If you added a filter to a previously created budget, the filter did not affect the budget when displayed in a user's view.
- Fixed bug: Microsoft Azure's Cost Center and Department Name fields did not work in filters. Also, you could not view the Show Information dialog for these fields from the Fields list.
- Fixed bug: For AWS resources in the US East (Northern Virginia) region, also known as us-east-1, the link from an Insights results table to edit the resource in the AWS portal did not work.
- Fixed bug: In reports, a column showing an average value for a field included empty values in the calculation of the average.
- Fixed bug: In the Views list, when you clicked the Default View it opened in editing mode even though that view is not editable.
- Fixed bug: In reports exported to CSV and Excel format, some numbers appeared in E notation instead of decimal notation.
- Fixed bug: Some Insights results were incorrect because numbers were averaged where they should have been summed.
- Fixed bug: When you removed all the pages from a view, the view was broken for users and could no longer be edited.
- Fixed bug: The Health Checks counter in the navigation menu counted health checks you had hidden.
January 10, 2017
On January 10, 2017 Cloud Cruiser released version 1.33.33, which includes the following enhancements and bug fixes:
- Creating or editing a view now follows a more intuitive path, letting you configure pages and widgets when you're ready.
- Microsoft Azure collections now run more efficiently and are able to pick up performance metrics for more VMs
- Fixed bug: Some data was lost during processing, resulting in missing usage and cost for a few customers with large amounts of usage data.
- Fixed bug: Some Insights result charts showed incorrect items in their titles
- Fixed bug: The first time you opened a previously-created budget in the new budget editor, you were prompted to save changes when closing even when you had made no changes
- Fixed bug: When exporting the results of an AWS-specific insight to CSV, some fields were missing in the export file
- Fixed bug: Budget notification emails were sent to inactive users
- Fixed bug: New customers had no example budget
- Fixed bug: When editing an insight, sometimes a number you entered was not saved
- Fixed bug: The user object sometimes didn't save properly
- Fixed bug: Some insight descriptions incorrectly used the words "Increasing" or "Decreasing" instead of "above" or "below"
December 21, 2016
On December 21, 2016 Cloud Cruiser released version 188.8.131.52, which includes the following bug fixes:
- Fixed bug: Entering a curly brace in the filter field search input was resulting in failures.
December 12, 2016
On December 12, 2016 Cloud Cruiser released version 1.32.8, which includes the following bug fixes:
- Fixed bug: No longer providing default pricing when prices were missing from AWS RI pricing sheets. Removed inaccurate RI advice and improper formatting
December 8, 2016
On December 07, 2016 Cloud Cruiser released version 1.32.8, which includes the following bug fixes:
- Fixed bug: Current Period Performance Chart was incorrectly showing future targets in budgeting rather than current period.
- Fixed bug: For users in GMT, the budget tooltips in detailed view was showing Q3 rather than Q4.
- Fixed bug: For users in GMT, future budget targets were showing up in future months charts.
- Fixed bug: For users in GMT, selecting Q1 - Q2 in budgets was displaying Q2 - Q3.
- Fixed bug: For users in GMT, budget drop downs were not giving the option to select Q4.
- Fixed bug: For budget users in Asian and European time zones, the current month or quarter was not being properly highlighted in grid data.
- Fixed bug: For users east of the GMT time zones, current quarter was not being properly displayed in budgets.
- Fixed bug: AWS collections failed on RDS subscription charges.
December 7, 2016
On December 07, 2016 Cloud Cruiser released version 1.32, which includes the following bug fixes:
- Fixed bug: Downloaded PDF reports were not working properly and giving a "Failed to load PDF document" error.
- Fixed bug: AWS collections failed to determine region for RDS instances.
- Fixed bug: Distributed reports were coming from the wrong email address and attachment names were being converted to all lower case.
- Fixed bug: AWS collections failed on RDS subscription charges.
December 06, 2016
On December 06, 2016 Cloud Cruiser released version 1.31.75, which includes the following enhancements and bug fixes:
- New feature: Budgeting in Cloud Cruiser 16 have updated. A significantly improved version of our existing budgeting functionality has been introduced giving users a host of new features. One of these new features is the ability to create budgets for more than a single target. For instance you can now specify a budget for "Departments" and see all children that fall under that selected field. Other improvements to be found in this version are the ability to view historical performance, budget sharing to groups and individuals, improvements to email notifications, and enhanced data viewing and analysis in the My View area.
For more information and instruction on using this feature, see Budgets.
- Added the ability to refresh list views from secondary toolbar.
- Fixed bug: Out-of-the-box reports with filters are using duplicate filters.
- Fixed bug: Launching to AWS portal from Insights is was broken.
- Fixed bug: Filters staying active after being deleted.
- Fixed bug: Wrong text for help link and wrong text in popover help bubble was being displayed in Manage Linked Accounts panel.
October 27, 2016
On October 27, 2016 Cloud Cruiser released version 1.30.31, which includes the following enhancements and bug fixes:
- For Microsoft Azure collections, the Details available for a subscription now include Connected On and Last Modified timestamps. The Connected On timestamp is only available for subscriptions connected after this release.
- Fixed bug: For Amazon Web Services collections, adding or deleting a linked account caused the original account to fail validation and prevented saving the collection.
October 19, 2016
On October 19, 2016 Cloud Cruiser released version 1.30.25, which includes the following enhancements and bug fixes:
- New in this release, the RI Advisor allows Amazon users to gain valuable insights and cost savings advice concerning your reserved instance usage. The RI Advisor will help you determine optimal coverage, recommending appropriate RI purchases, sales, and modifications to make. It can also help you understand break-even periods associated with different payment options, show you potential monthly cost savings, and display detailed transaction records not available in the AWS portal. One of the biggest advantages of the RI Advisor is the ability to perform purchase, sell, and modification actions directly within Cloud Cruiser. This removes the need to navigate through the complex and often confusing AWS portal.
For instructions on using this feature, see Using the RI Advisor to reduce AWS cost.
- Added the ability to export the Insights Drill Down results table to CSV format. This ability already existed in the Insights authoring view.
- Fixed bug: Creating a new linked account in IE 11 displayed outside the viewable area and ws unable to be scrolled to for viewing or editing.
October 11, 2016
On October 11, 2016 Cloud Cruiser released version 1.29.13, which includes the following enhancements and bug fixes:
- Fixed bug: AWS collector was at risk of collecting partial usage for several cycles starting after 4 PM PST.
October 7, 2016
On October 7, 2016 Cloud Cruiser released version 1.29.13, which includes the following enhancements and bug fixes:
- Added new KPI elements to the top of the What-if surface to help better visualize changes to virtual machines
- Fixed bug: Recollecting from Microsoft Azure collected data for the previous two months, and for earlier dates only reprocessed previously collected data. Manual recollection on Azure now recollects all previous months' bills to help ensure reporting is more complete and accurate.
- Fixed bug: In IE 11, the sign-in page was displaying the Microsoft and Google buttons incorrectly.
October 3, 2016
On October 3, 2016 Cloud Cruiser updated version 1.28 to add a new feature, What-If.
What-If allows you to model various changes to your virtual machines and see the impact to your cost. Compare the current state of your workload against possible future states, such as downsizing overprovisioned VMs, moving to a different region, or even switching cloud providers.
Each tenant's owner and any other users who are members of the Full Access group automatically have access to What-If. All others must be given the Manage What-If permissions capability. For more information, including a how-to video, see Using What-If to model changes.
September 29, 2016
On September 29, 2016 Cloud Cruiser released version 1.28, which fixes the bug that in the Reports page of your view, the Report list was not sorted. Now the report names in the list are sorted alphabetically.
September 23, 2016
On September 20, 2016 Cloud Cruiser updated version 1.27 with the following bug fixes:
- Fixed bug: A report that included both a pivot field and one or more groups showed columns in the wrong order.
- Fixed bug: If you clicked Save while editing an insight without making any changes, you received a 500 server error.
September 20, 2016
On September 20, 2016 Cloud Cruiser released version 1.27, which includes the following enhancement and bug fix:
- AWS data is now collected every two hours, giving you a more accurate and up-to-date view of your cloud usage.
- Fixed bug: For AWS collections, the Usage Start and Usage End time fields showed a larger period of usage for a given resource on a given day than actually occurred, even though the Quantity and Cost fields were correct. The bug is fixed for data collected from this point forward, but to correct historical data, you must recollect those dates. This bug occurred in the following two situations:
- When the resource was used two or more times during a day with down time in between, you received a single usage record with Usage Start set to the beginning of the first usage period and Usage End set to the end of the last usage period of the day.
- When Cloud Cruiser collected CloudWatch performance metrics for the resource, you received a single usage record with Usage Start set to 0:00:00 and Usage End set to 23:59:59.
September 12, 2016
On September 12, 2016 Cloud Cruiser updated version 1.26 with the following enhancement and bug fixes:
- Various Azure collector updates
- Fixed bug: When editing a Microsoft Azure collection, if you tried to export subscriptions before the Status column finished displaying, your exported file showed the wrong status for some subscriptions. Now the Export button is disabled until the subscription list has fully loaded.
- Fixed bug: Your subscription export was failing if one of the subscriptions was added by a Cloud Cruiser user account that no longer exists.
September 02, 2016
On September 02, 2016 Cloud Cruiser released version 1.26, which includes the following enhancements and bug fix:
- Cloud Cruiser now supports Single Sign On using Microsoft Azure Active Directory accounts and Google accounts. For more information, see Signing in with Microsoft or Google.
- If you don't add subscriptions while creating a Microsoft Azure collection, Cloud Cruiser prompts you to complete this important step with a dialog box that lists the benefits and provides a how-to video.
- Fixed bug: When you entered invalid AWS Credentials while updating an existing AWS Collection, there was no Error message.
September 01, 2016
On September 01, 2016 Cloud Cruiser updated version 1.25 with the following bug fix:
- Fixed bug: Report distribution failed for a large report (which takes more than 30 sec prep time) and you were not getting scheduled reports.
August 29, 2016
On August 29, 2016 Cloud Cruiser updated version 1.25 with the following enhancement:
- For AWS Data Sources, now you will see more VM property fields with data.
August 26, 2016
On August 26, 2016 Cloud Cruiser updated version 1.25 with the following enhancement:
- Make all field value selection offer as many values as does in the Filter Manager.
August 23, 2016
On August 23, 2016 Cloud Cruiser released version 1.25, which includes the following bug fixes:
- Fixed bug: When you opened My View (in a few specific scenarios only), you saw the message "An error occurred while checking if index exist: already exists."
- Fixed bug: If the cost bucket you specified for an AWS collection contains billing records from two or more accounts, collection could fail. This was because the collector read the first bill in filename order, which might not have matched the credentials you entered.
August 17, 2016
On August 17, 2016 Cloud Cruiser updated version 1.24 with the the following bug fix:
- Fixed bug: SmartTags preview section is not working.
August 15, 2016
On August 15, 2016 Cloud Cruiser released version 1.24, which includes the following enhancements and bug fixes:
- For AWS collections, the fields that contain VM properties (for example VM CPU Count and VM Disk GB) are now populated for usage records for products such as Amazon RDS that run on top of user-selected VM instances.
- Fixed bug: When removing a column from a report, if that field was also used as a group you received an error message and could not remove the column.
- Fixed bug: After setting a field to Hidden in the Data > Fields page, a browser refresh was required before that field was treated as hidden.
- Fixed bug: When editing the SmartTags rules for a Microsoft Azure collection, sometimes the preview table was empty.
- Fixed bug: If you signed up for a Cloud Cruiser trial from our website using an address that had been previously used to sign up but which had not been verified yet, another verification email message was not sent.
August 9, 2016
On August 9, 2016 Cloud Cruiser updated version 1.23 to fix a bug with the new Purchase Model field for AWS collections. The field was not being set for Redshift, ElastiCache, and RDS resources.
August 5, 2016
On August 5, 2016 Cloud Cruiser updated version 1.23 with the following enhancements and bug fixes:
- Now Forecasting supports three calculation methods: Simple Moving Average and Weighted Moving Average have been added to Linear Regression, which was the only available method before. You select your desired calculation method from the new Method menu on the Forecasting page.
- Fixed bug: On a Chromebook client, Insights did not display any results.
August 3, 2016
On August 3, 2016 Cloud Cruiser updated version 1.23 with the following enhancements and bug fixes:
- AWS collections now populate Blended Rate and Blended Cost fields, giving you more ways to track the cost of reserved instances. The Rate and Cost fields continue to reflect unblended rate and cost.
- AWS collections now populate another new field, Purchase Model. This field shows whether the usage in a row occurred as an On Demand, Reserved, or Spot instance.
- Injected line items from your AWS bill are now processed differently to better show you the unused portions of your instance reservations. These line items now show their Units as Unused-Instance-Hours, with Quantity representing the unused hours and Rate the rate for those hours as found in the bill, and Cost being the multiple of those two numbers. This allows you to easily build a report such as the one below to see where you are wasting money on reservations that are not being used.
- Fixed bug: The Operating System field was not populated for AWS resources.
August 1, 2016
On August 1, 2016 Cloud Cruiser updated version 1.23 to give Insights the most recent view of your data across all collections. For each collection, an insight determines the most recent date for which Cloud Cruiser has collected data, and then it uses the oldest of those dates as the end of the time period to evaluate. Previously, Insights was one day behind this.
July 27, 2016
On July 27, 2016 Cloud Cruiser released version 1.23, which includes the following enhancements and bug fixes:
- Fixed bug: For AWS spot instances, VM property fields such as VM CPU Count, VM Disk Type etc were not being populated. To populate these fields for past dates, you must run SmartTags rules for those dates.
- Fixed bug: Health Check page was showing both Active and Hidden health checks by default.
July 26, 2016
On July 26, 2016 Cloud Cruiser released version 1.22, which includes the following enhancements and bug fixes:
- Better messages to users when a report fails to return data or returns incomplete data, suggesting ways to modify the report to succeed.
- Numeric fields are now displayed with their unit of measure across the entire application, helping you understand the meaning of numbers you see. You can change the unit of measure that is displayed for a field. For instructions, see Creating fields.
- Budget notification email messages now use a Subject line that tells you which budget and which threshold a message pertains to, giving you more visibility from your inbox without opening the message. Example:
50% threshold exceeded for budget "Service Category = Compute"
- Fixed bug: When using the Edge browser, navigating to Data > Fields displayed an empty window until you refreshed your browser.
- Fixed bug: In the Forecasting page, sometimes numbers on the Y axis overlapped the key, making both hard to read.
July 22, 2016
On July 22, 2016 Cloud Cruiser updated version 1.21 to remove future dates from charts when the Period is set to Current Month, Current Quarter, or Current Year. These future dates would have no usage and thus be empty areas on the chart. Selecting one of these periods now gives you a "to date" chart.
July 18, 2016
On July 18, 2016 Cloud Cruiser released version 1.21, which includes the following enhancements and bug fixes:
- Health Checks now look more consistent with the rest of the application.
- Fixed bug: When authoring an insight, fields and text were not visually aligned.
- Fixed bug: Google Cloud Platform collections occasionally failed to collect data for a day.
- Fixed bug: A report embedded in a page using a Report Widget sometimes did not display any rows until the user clicked a chart or otherwise modified a filter on the page.
- Fixed bug: Insights results stopped updating when a collection was set to Inactive.
July 14, 2016
On July 14, 2016 Cloud Cruiser updated version 1.20 to remove the Hourly frequency option from report distribution because data is only collected on a daily basis. Reports currently set for hourly distribution will continue to be sent hourly until you edit their distribution settings, at which point you must choose a different frequency.
July 7, 2016
On July 7, 2016 Cloud Cruiser updated version 1.20 with the following bug fixes:
- Fixed bug: A null value in a lookup prevented the lookup from being used by SmartTags rules.
- Fixed bug: Occasionally, a report would fail to export to a file. This happened both when a user requested an export and when a scheduled report ran.
June 30, 2016
On June 30, 2016 Cloud Cruiser updated version 1.20 with the following enhancement and bug fixes:
- Cloud Cruiser now processes lookup tables faster, resulting in improved performance when you load and open large lookups. See Lookups for more information about uploading and creating lookups.
- Fixed bug: Cloud Cruiser was not displaying some VMs in analytics, though information for those VMs was collected.
- Fixed bug: The Help button on the Edit Lookup screen opend the wrong Help dialog.
June 28, 2016
On June 28, 2016 Cloud Cruiser updated version 1.20 to support uploaded lookup files as large as 10 MB. Additionally, if you import a lookup file with more than 2,000 rows, you can now edit that lookup in Cloud Cruiser. Prior to this change, you could not edit imported lookups with more than 2,000 rows. For more information about using lookup files to supplement your collected cloud billing and usage data with business information, see Lookups.
You can use any of the following browsers:
- Google Chrome 42 and later
- Microsoft Edge 20 and later
- Microsoft Internet Explorer 11 and later
- Mozilla Firefox 38 and later
You can use Cloud Cruiser from any operating system that can run a supported browser. However, if you are using a Microsoft Windows Server operating system, you must turn off the
IE Enhanced Security Configuration option.
To turn off the IE Enhanced Security Configuration option
- Open Microsoft Windows Server Manager.
- In the navigation pane, select Local Server.
- Next to the IE Enhanced Security Configuration option, click On.
- In the dialog box, change the settings for Users and Administrators to Off, and then click OK.
Microsoft Windows Server Manager updates to show the IE Enhanced Security Configuration option as Off.