Home > Release Notes (public) > Cloud Cruiser 16 Release Notes > Archive of Cloud Cruiser 16 release notes

Archive of Cloud Cruiser 16 release notes

This topic describes the enhancements and bug fixes in older versions of Cloud Cruiser. For information about more recent releases, see Changes in recent releases.

April 25, 2017

On April 25, Cloud Cruiser released version 1.41.10, which includes the following enhancements:

  • For Azure virtual machines in a subscription connected to Cloud Cruiser, two new metric fields are collected: Memory Available and Memory Utilization.
  • Costs can now be viewed in Chinese Yuan.
April 13, 2017

On April 13, Cloud Cruiser released version 1.41.8, which includes the following enhancement and bug fix:

  • In Reports, the Report Configuration Panel field names now use all of the available white space.
  • Fixed bug: In the Budgets feature, the Current Period Performance chart showed zeroes on the Y axis.
April 12, 2017

On April 12, Cloud Cruiser released version 1.41.6, which includes the following enhancement and bug fixes:

  • Azure collections help text now states that Cloud Cruiser accepts Enrollment Access Keys and does not accept keys below that level.
  • Fixed bug: After creating a new View, the Edit button did not open the Edit View page.
  • Fixed bug: Contact Cloud Cruiser list of features did not include Budgets, What-If or RI Advisor.
March 31, 2017

On March 31, Cloud Cruiser released version 1.41.3, which includes the following bug fix:

  • Fixed bug: For Insights, in the Complete Result Set table, clicking the Resources link resulted in an Access Denied message.
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.
    Screenshot of Active Processes dialog
     
  • 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 1.37.1.1, 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 1.32.8.1, 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

    Central  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.

RI Advidsor

  • 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.

What-If service catalog.png

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.
    AWS - Unused RI Hours report
  • 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.

June 23, 2016

On June 23 Cloud Cruiser updated version 1.20 to improve the efficiency of back-end collection processes and system reporting.​

June 22, 2016

On June 22, 2016 Cloud Cruiser updated version 1.20 with the following bug fixes:

  • Fixed bug: On the Fields page, searching for a field displayed that field in the same place it was in the main list, and not at the top of the list. This could cause some search results to appear off screen unless you scrolled down.
  • Fixed bug: In the Reports widget in Views, sorting by a numeric column did not sort correctly.
June 21, 2016

On June 21, 2016 Cloud Cruiser updated version 1.20 to ensure that the most recent Azure data available is collected.

June 20, 2016

On June 20, 206 Cloud Cruiser updated version 1.20 to improve reporting performance, and to fix a bug in the report authoring screen that showed a warning message with number larger than 10,000 when a report would include more than the maximum 10,000 rows of data.

June 17, 2016

On June 17, 2016 Cloud Cruiser updated version 1.20 to fix an bug that could cause AWS data to be removed from Cloud Cruiser when the date for that data changed on the AWS bill.

June 16, 2016

On June 16, 2016 Cloud Cruiser released version 1.20, which includes the following enhancements and bug fixes:

  • An improved Cloud Cruiser collections display now makes it easier for you to see the status of your data collections, and to identify the range of any missing data. On the main list of collections, Cloud Cruiser shows the Earliest Date to Collect you specified for the collection, and shows whether your collection is missing any data in the current quarter. A status icon indicates whether collection for that quarter succeeded (​), or failed ().


    Click the status icon to open a dialog that shows the collection status for each day since the Earliest Date to Collect. Green segments indicate successful collections of data, while grey segments indicate data is missing for some days. If you mouse over a grey segment, Cloud Cruiser displays the range of dates for that segment, making it easier for you to identify the range you need to enter when recollecting data. For more information about recollecting data, see Starting collection manually.
  • Fixed bug: Cloud Cruiser could not process some email domains, causing the sign-up process to freeze.
  • Fixed bug: When creating an Insight, selecting the Numeric level sustained for a group template and then changing to a different template sometimes caused Cloud Cruiser to run very slowly.
  • Fixed bug: For AWS data, Cloud Cruiser was returning negative values for the Storage Read Bytes and Storage Write Bytes fields.
  • Fixed bug: Exporting a report produced a "no such index" error.
  • Fixed bug: When you attempt to create a report with more than 10 columns, Cloud Cruiser returned an "Error" dialog instead of letting you know that you added too many columns.
  • Fixed bug: Due to the way Amazon processes charges and credits, there were sometimes small differences between the amounts shown on the AWS bill and the data displayed in Cloud Cruiser.
June 7, 2016

On June 7, 2016 Cloud Cruiser released version 1.19, which includes the following enhancements and bug fixes:​

  • Cloud Cruiser now allows you to select whether a field is Visible or Hidden in lists of fields, uncluttering the lists and making it easier for you to create the analytics you need. For example, Cloud Cruiser might create several new fields based on tags it discovered during collection, but you might not need many of those fields in Cloud Cruiser. You might also create a new field to use only as part of a SmartTags calculation, but won't ever need to use that field in a chart or report.

    Hiding a field only removes it from lists of fields. If a field is already being used in a report, for example, hiding the field does not remove it from the report.

    When viewing lists of fields, you can choose to show hidden fields by clicking Show Hidden Fields at the bottom of the list. When you do this, Cloud Cruiser shows the hidden fields in italics.

    For more information about showing and hiding fields, see Fields and field packages.
  • When authoring a report, you can now toggle whether to show or hide Hidden fields in the list of fields. This enhancement allows you to simplify your display by shortening the list of fields to include only those that should be used. For more information about creating reports, see Reports.
  • You might have several fields in Cloud Cruiser, especially if you have multiple collections for different cloud providers. To make it easier for you to find fields you have collected, on the Fields page you can now use the Group icon () to select how you want your fields to be listed: by the date they were added, by their types, or by visibility. For more information about viewing fields, see Fields and field packages.
  • Fixed bug: When editing an Azure collection and repeatedly clicking Save, Cloud Cruiser added duplicate subscriptions to your collection. In addition to fixing this bug, Cloud Cruiser has removed any duplicate subscriptions you might have created accidentally.
  • Fixed bug: When creating a report, selecting a date range before adding columns caused the report to display: ERROR.
  • Fixed bug: The Groups page showed an incorrect number of users in some groups.
June 1, 2016

On June 1, 2016 Cloud Cruiser updated version 1.18 with the following bug fixes:

  • Fixed bug: Cloud Cruiser did not populate the Provider Region field in Cloud Cruiser with the Availability Zone field values set in AWS.
  • Fixed bug: You could not edit filters on the Reports page of your View.
May 25, 2016

On May 25, 2016 Cloud Cruiser released version 1.18, which includes the following enhancements and bug fixes:​

  • The top bar of each main page now remains visible when you scroll the page. This enables you to scroll down to browse your list items while the tool icons and page title remain visible without having to scroll back up. Similarly, when you scroll down a View page, the tabs remain visible, enabling you to switch pages without having to scroll back up.
  • If the names of all tabs in a View don't fit next to each other within your browser window (due to a large number of tabs, long names, a narrow window, or a combination of these), the tabs now display in a single scrollable row instead of wrapping to a second row. This enables more of your View to remain visible.
  • Lists of items on main pages now load much faster. For example, the Data > Fields page now loads the list of fields faster.
  • Fixed bug: When loading a report on the Reports page of a View, Cloud Cruiser did not display a spinner, making it difficult to understand that the report was loading.
  • Fixed bug: When loading a report on the Reports page of a View, the report covered the Filter and Period fields.
  • Fixed bug: The Upload button was missing the first time you visited the Lookups page.
May 24, 2016

On May 24, 2016 Cloud Cruiser released a hotfix to version 1.17, fixing a bug that prevented you from selecting some field values in the Filter Manager dialog. When creating a filter, you can type in the Selected Values field to search for the value you want. However, if the value you wanted was not in the first 2000 values initially listed, you could not select that field. This hotfix corrects that bug.

May 23, 2016

On May 23, 2016 Cloud Cruiser released a hotfix to version 1.17, fixing a bug that prevented some users from adding subscriptions to Azure collections when using the Edge Web browser.

May 16, 2016

On May 16, 2016 Cloud Cruiser released version 1.17, which includes the following enhancements and bug fixes:​

  • This release introduces a new health check, which alerts you when an Azure collection has enabled subscriptions to which Cloud Cruiser is not connected. Click Manage Subscriptions in the Health Check to either add these subscriptions again using sufficient credentials or disable collection for them. For more information about Health Checks, see Health checks. For more information about adding subscriptions to an Azure collection, see Microsoft Azure.
  • Cloud Cruiser now includes the Resource Name field to help you identify your cloud resources by name instead of just by ID (the Resource ID field). For more information about the fields available in reports and charts, see Field mapping.
  • When creating or editing a report, the date range you select is now used as the default date range when that report is opened in Views. This enables you to create and distribute monthly and quarterly reports, for example. You can temporarily select a different date range using the Period field in your View. If you frequently need to view a different date range for that report, consider making a copy with a different range. For more information about creating reports, see Reports.
  • When creating or editing reports, any filter you add to that report is saved with that report. If you share that report with other users, they can add their own filters, but they cannot remove the filters you defined as part of the report. These locked filters are shown with a lock icon. For more information about creating reports, see Reports.
  • You can now configure donut charts to display up to 20 segments, an increase from the previous maximum of 5. For more information about configuring donut charts, see Chart widgets.
  • Fixed bug: In budget alert emails, field names and tags appeared as strings of numbers.
  • Fixed bug: Editing an Upload Usage API collection failed with the message: "Unable to create data source: Upload Usage API. Cause: Not Found (status = 404)"
  • Fixed bug: For AWS resources, links to the AWS portal were missing from insights tables.
  • Fixed bug: Budget emails were not being sent.
  • Fixed bug: Values for Azure tags were not appearing in reports.
  • Fixed bug: Lookup tables lost values when only the name of the table was changed.
May 4, 2016

On May 4, 2016 Cloud Cruiser released version 1.16, which includes the following enhancements and bug fixes:​

  • When configuring a line chart for a view, you can now select Week as a Time Interval, giving you more options for how to view your cloud data. For more information about adding charts to a view, see Views.
  • The Previous and Next buttons are now always visible on the Subscriptions page of the Azure collections wizard. If you have a long list of subscriptions, you no longer need to scroll down to see the navigation buttons.
  • When creating a new decimal or integer field, you can now select a Unit of Measure to display next to values in charts. You can also select whether the new field should be treated as a Currency field. If it is a Currency field, a dollar sign ($) is automatically used for the Unit of Measure. These options give you more control over how your cloud data is displayed in charts and reports. For more information about creating fields, see Fields and field packages.
  • Fixed bug: The following Insights templates showed "undefined" in the Rule Definition: Cost increase for a group, CPU Utilization change for a group, and Quantity change for a group.
  • Fixed bug: The Reset link was missing from widgets after filtering by clicking in the widget.
  • Fixed bug: The Period field in the Reports widget was displaying no values.
  • Fixed bug: When adding a new widget to a View that already had a filter defined, the new widget was not affected by the filter.
  • Fixed bug: Typing a date range for a report did not change the data displayed in the report.
  • Fixed bug: Filters defined for a View page did not persist for the Report widget on that page.
April 29, 2016

On April 29, 2016 Cloud Cruiser released a hotfix to version 1.15.6. This release fixes a bug that prevented you from updating credential information in your collections.

April 21, 2016

On April 21, 2016 Cloud Cruiser released version 1.15.6, which includes the following enhancements and bug fixes:​

  • When Cloud Cruiser cannot connect to an Azure subscription, the Subscriptions list now shows the reason.
  • Fixed bug: Due to a change in the Microsoft Azure billing file format, Cloud Cruiser was temporarily unable to collect Azure data.
  • Fixed bug: After adding new subscriptions to an Azure collection, only one day of historical data was collected.
April 19, 2016

On April 19, 2016 Cloud Cruiser released version 1.14.26, which includes the following enhancements and bug fixes:​

  • The Microsoft Azure Subscription list has been redesigned to make it easier for you to manage the subscriptions included in your Azure collections. For more information about configuring Azure collections, see Microsoft Azure.
    • The Collect checkbox replaces the Status Enabled/Disabled toggle, and determines whether a subscription will be included when Cloud Cruiser collects usage and other data.
    • You can now search for subscriptions in the list.
    • The Subscription GUID is displayed for each subscription, and if the Name is truncated you can hover your mouse pointer to see the full subscription name.
    • You can click a Details icon to display information about the subscription, including two new fields to help you identify who added the collection. The Connected By (Live ID) field shows the Microsoft Account used to add the collection. The Connected By (user) field shows the Cloud Cruiser user who added the collection.

  • The AWS Linked Accounts list has been redesigned to make it easier for you to manage the linked accounts in your AWS collections. A new capability enables you to search for linked accounts in the list. For more information about configuring AWS collections, see Amazon Web Services.

  • In the Collection Status dialog, the Data Source column now lists the name of each collection. Prior to this change the column listed the cloud provider of each collection. This change helps you differentiate between multiple collections of the same provider. For more information about collections, see Collections.
  • When editing a view, any filters you add to a Filter widget are saved with the view. Users who are assigned that view can see and add to the filters, but not remove them. This lets you target a page to a particular segment of your data, such as VMs. For more information about creating views, see Views.
  • When creating filters you can now use the Starts with operator to filter data by fields that start with the text you enter. For more information about creating filters, see Filtering data.
  • Fixed bug: Filters were not changing the data displayed in some charts.
  • Fixed bug: After adding a filter to an insight you could not remove the filter.
  • Fixed bug: In AWS collections, setting a linked account to Inactive and then back to Active resulted in an error: Invalid Credentials All accounts must be valid OR set to inactive to save datasource.
  • Fixed bug: Trying to copy an insight produced an error: 405 Method Not Allowed.
April 11, 2016

On April 11, 2016 Cloud Cruiser updated version 1.13 with the following enhancements and bug fixes:

  • In your collections, Cloud Cruiser now displays a small dashboard for the status of each subscription for (Azure collections) or linked account (for AWS subscriptions. Click a status icon to filter the subscription list by that status. For example, click the checkmark to show only connected subscriptions. For more information about creating collections, see Collections.
  • For insights grouped by Resource ID, in the table you can now click a box next to AWS VMs and EBS volumes, and Azure VMs to open those resources in the AWS or Azure portal, as appropriate for the resource. For more information about creating insights, see Insights.
  • When creating filters you can now use the Is empty and Is not empty operators to filter data by fields that either have no value or any value. For more information about creating filters, see Filtering data.
  • If negative values exist, horizontal bar charts now show negative values on the x-axis. For more information about adding charts to views, see Views.
  • You can now configure charts to display up to 30 bars or lines. Prior to this change charts displayed up to 5 bars or lines.
  • Fixed bug: Data collection was not running automatically every night.
  • Fixed bug: Using the gear icon to open a report for editing displayed an empty report.
  • Fixed bug: Cloud Cruiser was not saving edits to Insights.
March 29, 2016

On March 29, 2016 Cloud Cruiser updated version 1.13 with the following enhancements and bug fixes:

  • You can now choose to show or hide the graph displayed for insights. Additionally, Cloud Cruiser remembers your choice for all insights you open. For more information about creating insights, see Insights.
  • Fixed bug: Clicking the navigation arrows in the product tour produced an error message.
  • Fixed bug: When saving a view, Cloud Cruiser incorrectly displayed the text, "Changing an existing name creates a copy of the view"
  • Fixed bug: If authentication failed for one AWS linked account, no metrics were collected for any of the linked accounts.
March 22, 2016

On March 22, 2016 Cloud Cruiser released version 1.13, which includes the following enhancements and bug fixes:​

  • If a user attempts to enter a URL directly to open a page that they do not have permission to open, that user is now redirected to the My View page.
  • Fixed bug: When a filter is defined for a report, switching between Editing and Viewer modes caused the Filter dialog to flicker on screen.
March 20, 2016

On March 20, 2016 Cloud Cruiser released version 1.12, which includes the following enhancements and bug fixes:

  • You can now export details about forecasted data to a CSV file. Fore more information about using Forecasts to project the future of your cloud usage and spend, see Forecasting page.
  • Fixed bug: Clicking Validate failed to validate linked accounts in an AWS collection.
  • Fixed bug: When creating an AS collection, trying to proceed past step 2 of the wizard while one or more accounts have invalid credentials produced an invalidClientTokenId error.
  • Fixed bug: The Forecasting widget showed an incorrect name temporarily.
  • Fixed bug: On Firefox browsers, the Filter button on the Forecasting widget did not work.
  • Fixed bug: When using filters in the Forecasting widget, unselecting the Show Actuals option did not hide historical data.
  • Fixed bug: In Forecasts and Insights, data in the chart and table did not match.
March 17, 2016

On March 17, 2016 Cloud Cruiser released version 1.11, which includes the following enhancements and bug fixes:

  • The report authoring experience has been enhanced to make it easier for you to see your data as you write a report. For more information about writing reports, see Reports.

    • You can now toggle between an editing mode and a viewer mode. When editing, the report authoring environment includes a report configuration panel that enables you to add and organize fields, filter data, determine numeric aggregation methods, and so on. The viewer mode hides that panel so you can better see how your report will appear to other users.
    • You can now use Period fields, located above the table, to select a date range when authoring a report. When you save the report, by default it will display data only for the range you selected.
    • Reports now include a summary row at the bottom of the report so you can see totals for columns.
  • The Insights display has been enhanced to make it easier for you to see information about situations in your cloud that could be costing you money.  For more information about configuring Insights, see Insights.

    • The bar graph in the Insight Results area now shows the previous average and the current average for each group, as well as the percentage change that represents. Prior to this change, the bars showed the percentage change and raw-value change.
    • You can now toggle whether the bar graph appears for an insight by clicking Hide Visualization/Show Visualization.
    • Because the red line indicates the thresholds set for the insight, and is the only line needed in the chart, the yellow line for the Approaching status has been removed. If you need more information about items approaching alert status, see the Insight Status column in the table below the chart.
    • The Alert Status bar has been replaced by a small dashboard above the table, and shows how many items are in each state: Normal, Approaching, and Alert.
  • Cloud Cruiser has enhanced the forecasting capabilities available to you. For more information about forecasting the future of your cloud, see Forecasting page.
    • You can now add a Forecasting widget to any page of a view. Prior to this change, if you wanted forecasting in a view you needed to create a page dedicated to forecasting. If the Forecasting widget is on a page with date range fields and and/or filters, the data used in the Forecast widget is limited by the selected date range and filters.
    • The Forecasting widget now includes an Expand Details icon that enables you to see detailed tabular data for your forecast.
  • If you have permission to edit views, you can now do so directly from the My View page. For more information about editing views, see Views.
  • Cloud Cruiser includes a new Resource Type field. If you want to see only VM data in charts and reports, you can now create a filter for "Resource Type Is VM".
  • Fixed bug: After creating an AWS collection, you could not edit that collection to add linked accounts.
  • Fixed bug: Copying a report overwrote the existing report.
  • Fixed bug: On the Collections page, Cloud Cruiser was showing a collection history for the most recent 4 days instead of the most recent 5 days.
  • Fixed bug: When editing an insight, the Category and Recommendation fields were empty.
  • Fixed bug: Removing a condition or action from a SmartTags rule did not remove that condition or action from the rule summary area.
March 9, 2016

On March 9, 2016 Cloud Cruiser released version 1.10, which includes the following enhancements and bug fixes:

  • For Azure collections, Cloud Cruiser now collects Resource Group names. You can now include resource group data in your reports, charts, and other Cloud Cruiser analytics tools. For more information about collecting Azure cost and utilization data, see Microsoft Azure.
  • When creating an AWS collection, Cloud Cruiser now validates the AWS linked account credentials you entered before allowing you to proceed to the next page in the collection wizard. For more information about creating AWS collections, see Amazon Web Services.
  • The VM Utilization and VM Details reports now have filters that more accurately list the VMs in your cloud. For more information about using reports, see Reports and Viewing usage and billing data.
  • You can now distribute reports by email to any Cloud Cruiser user and group. Prior to this change, you could only distribute reports to users and groups with permission to use the report. For more information about distributing reports, see Reports.
  • Because the Field is Empty and Field exists SmartTags conditions were serving the same functional purpose, the Field exists condition has been removed. Use the Field is empty condition to identify rows of data where a field either has a value or does not have a value. For more information about using SmartTags conditions, see Conditions in SmartTag rules.
  • When creating a filter, the values available for the field you select now depend on the data you collected over the past 90 days. Prior to this change the values available depended on the data you collected over the past 30 days. This gives you more flexibility when filtering data. For more information about creating filters, see Filtering data.
  • Fixed bug: Adding a filter to a widget changed the Period field for the entire My View page containing that widget.
  • Fixed bug: In reports, the Total row was showing empty values for columns with large values.
  • Fixed bug: If you had no current data collected, you could not create a budget in you View.
February 25, 2016

On February 25, 2016 Cloud Cruiser released version 1.9, which includes the following enhancements and bug fixes:

  • You are now notified when a new version of Cloud Cruiser is available. If you are logged out when the new version become available, a message notifies you about the upgrade after you log in. If a new version becomes available while you are already logged in, a message lets you know about the new version, and prompts you to save your work before upgrading.
  • When creating an AWS collection, Cloud Cruiser now validates the AWS payer account credentials you entered before allowing you to proceed to the next page in the collection wizard. For more information about creating AWS collections, see Amazon Web Services.
  • If you group data in a report, and a row of data is missing a value for the group field, that row is now grouped in the (no value) group. For example the following image shows a report grouped by Billing Code. Five rows of data are missing a Billing Code value, so they are grouped in the (no value) group. For more information about creating reports, see Reports.
    noValue.png
  • When saving a report or insight, you can now select the Share with all users option to make the report or insight available to everyone. Reports and insights included in Cloud Cruiser by default have this option selected already. For more information about creating reports, see Reports. For more information about creating insights, see Insights.
  • You can now copy reports, lookups, fields, groups, and field packages from the main lists of those items. To copy any of these items, next to the item you want to copy click the gear icon and select Copy. For example, the following image shows how to copy a report from the main list of reports:
  • Similarly, from the main lists of items you can now see the properties of views, insights, lookups, and field packages. To do so, click the gear icon and select Properties.
  • On the Reports page, you can now toggle whether email distribution of a report is active or inactive. To do so, click the gear icon and select Toggle Distribution. For more information about reports, see Reports.
  • On the SmartTags page, you can now toggle whether the SmartTags defined for a collection are active or inactive. To do so, click the gear icon and select Toggle Status. For more information about SmartTags, see SmartTags.
  • Fixed bug: After a failed Azure collection, Cloud Cruiser displayed two health checks instead of one.
  • Fixed bug: After adding a filter in the Filter Manager, clicking Add Filter did not allow you to create a second filter.
  • Fixed bug: After creating a new budget, you could not edit the budget amount.
February 11, 2016

On February 11, 2016 Cloud Cruiser released version 1.8 which includes the following enhancements and bug fixes:

  • Cloud Cruiser has made several improvements to Insights:
    • New customers now receive four additional default insights to find cost savings opportunities in your AWS environment:
      • Underutilized EBS volume
      • Underutilized ElastiCache host
      • Underutilized RDS instance
      • Underutilized Redshift node
    • New rule templates are available so that you can create your own custom insights based on the utilization of Amazon EBS, ElastiCache, RDS, and Redshift.
    • When you save an insight, the description of that insight is now updated automatically after every saved change, so the description reflects the rule accurately.
    • Mousing over thresholds in an insight now displays details about that threshold.
    For more information about creating insights, see Insights. For more information about viewing insights in your View, see Working with charts and reports.
  • Cloud Cruiser can now collect Amazon CloudWatch performance and utilization data for all accounts linked to your payer account. For more information about creating AWS collections, see Amazon Web Services.
  • When adding subscriptions to an Azure collection, you must sign in to Azure. The dialog box for this is prevented from opening if your browser is configured to prevent pop-ups. Cloud Cruiser now prompts you to turn off pop-up blockers when adding subscriptions to your Azure collection. For more information about creating Azure collections, see Microsoft Azure.
  • Fixed bug: Due to multiple changes Microsoft made to the format of their Azure Billing files, Azure collection was not working.
  • Fixed bug: When you created a chart with a Value Field that has no data, the chart did not display properly.
  • Fixed bug: Creating an AWS collection resulted in server errors.
  • Fixed bug: After grouping a column in a report, the original ungrouped column was still displayed.
  • Fixed bug: You could not ungroup columns in a report.
  • Fixed bug: Report distributions that were supposed to include an Excel version of the report did not include the Excel file.
January 29, 2016

On January 29, 2016, Cloud Cruiser released version 1.7, which includes the following enhancements and bug fixes:

  • When you create a collection, Cloud Cruiser now lets you know when a required field is missing a value. For more information about creating collections, see Collections.
  • Forecasting now uses a single, more accurate algorithm for forecasting the future of your cloud. For more information about forecasting, see Forecasting page.
  • From the context-sensitive help dialog, you can now open the full documentation site in a new browser.
  • Fixed bug: You could not delete budgets from your View. For more information about using budgets, see Budgets page.
  • Fixed bug: You could not delete reports with inactive distribution lists. For information about distributing reports, see Reports.
January 25, 2016

On January 25, 2016, Cloud Cruiser released version 1.6, which includes the following bug fixes and enhancements:

  • Cloud Cruiser can now collect usage and billing data from Google Cloud Platform. For information about configuring Google Cloud Platform and creating a collection in Cloud Cruiser, see Google Cloud Platform.
  • Cloud Cruiser administrators can now enable users to create their own reports in their View by granting the Manage Personal Reports permission. Sharing reports and editing shared reports requires the Manage Shared Reports permission.
    • For more information about creating and sharing reports, see Reports.
    • For more information about permissions, see Permissions.
  • Cloud Cruiser has updated the list of supported browsers.
January 19, 2016

On January 19, 2016, Cloud Cruiser released the following enhancements and bug fixes:

  • AWS collection is now faster. For more information about creating AWS collections, see Amazon Web Services.
  • Fixed bug: For AWS collections, the Account Name field to displayed the account number instead of the account name. The field now displays the account name.
January 5, 2016

On January 5, 2016, Cloud Cruiser released the following enhancements and bug fixes:

  • Azure collection now includes resource tags. For more information about creating an Azure collection, see Microsoft Azure.
  • Fixed bug: After a failed Azure collection, Cloud Cruiser did not start the next scheduled collection.
  • Fixed bug: You could not edit lookups you uploaded to Cloud Cruiser. For more information about using lookups, see Lookups.
December 22, 2015

On December 22, 2015, Cloud Cruiser released the following enhancements and bug fixes:

  • You can now include Azure subscriptions as part of your Azure collections. For more information, see Microsoft Azure.
  • The Insights Summary and Insights Drilldown now load faster. For more information about creating insights, see Insights. For information about using the Insights Summary in your view, see Insights Summary.
  • Fixed bug: Azure insights older than 5 days did not appear in the Insights Summary.
You must to post a comment.
Last modified
17:31, 8 Aug 2017

Tags

This page has no custom tags.

Classifications

This page has no classifications.