Locale selector icon
Nov202005

Update to Partner Customer Success Service - Customer Health Analytics

As a part of our Partner Customer Success Service (CSS), we’re excited to announce the availability of Customer Health Analytics. Customer Health Analytics provides you with detailed analysis of the health of your cloud business and the health of your customers’ cloud environments, benchmarked against their peers. 

Key deliverables include:

  • Visibility into your cloud business across key metrics, including net retention, cloud spend per customer, changes in cloud spending over time, and variance against spending forecasts. 

  • A health score that is developed using your customers’ actual implementation and thousands of data points captured from you and your customers over time. 

  • Monthly analysis and go-to-market expertise. Each month, your CloudHealth Technical Account Manager (TAM) will analyze the data and give you actionable insights. With your TAM, you can drill down visually into health scores for specific customers. You’ll know whether you’re trending in the right direction and get recommended actions to take to maintain and increase health scores over time.

For more information about the Partner Customer Success Service and Customer Health Analytics, please contact your partner TAM or visit the CloudHealth Partner Portal.

Updates to Kubernetes Reporting - Now Available

We’re pleased to announce significant improvements to the underlying technology of our containers reporting, building a foundation for future enhancements. To improve reporting and make your CCoE successful as you modernize your applications, we have made the following changes: 

  • Faster load times for Kubernetes Resources and Allocation Reports.

  • Extended data timeline (13 months) for Kubernetes Resources and Allocation Reports, and Containers Cost Distribution in the Containers Cost History Report for Kubernetes environments.

  • Updated configuration and terminology of usage reports:

    • Task Family and Task are no longer configurable reporting buckets (for Namespace, Container Image, or Pod Label), but instead CloudHealth will by default report on Namespace, Container Image, and up to 6 Pod Labels of your choice (in addition to, and similar to, how Node Label reporting can be configured). The flexible configuration framework and more abstract terms were useful for some use cases, but also created confusion. Instead we’ll now provide this superset functionality using core Kubernetes dimensions by default for usage reports. For environments with many (1000s) of dimension values (e.g. namespaces) CloudHealth continues to recommend starting by filtering to the cluster of interest and introspecting from there.

    • CPU and Memory requests, also used by containers for cost distribution, are no longer labeled “Used CPU” and “Used Memory” but rather “Requested CPU” and “Requested Memory.”

  • Improvements to data aggregation.

Note: These changes mean saved bookmarks, saved reports, and subscriptions will need to be updated for Kubernetes Resources, Kubernetes Allocation, and Containers Cost History Reports. CloudHealth has taken extra steps to create new saved reports and subscriptions to replace your current ones, but please verify these as some may require minor adjustments and a re-save given the nature of the terminology and configuration changes.

Updates to FlexReports

Support for Subscriptions

We have added support for creating subscriptions for FlexReports, so you don't have to  manually generate and export your FlexReports. You can create subscriptions based on a calendar period (daily, weekly, monthly) and an email will be sent with the link to download the report in a CSV format, to the intended recipients on the set date-time. Once a subscription is created, you can view the list under 'Manage Subscriptions' and you will be able to edit or delete it as needed. 

Support for FlexOrgs Hierarchy

With the introduction of FlexReports, you were able to create reports only at the top level organization of the FlexOrgs hierarchy, today, we’re happy to announce that is no longer the case. You are now able to have the complete 'Flex' experience with FlexReports working together with FlexOrgs -- FlexReports can now be created at a specific sub organization level so that associated users can query data in the scope of that organization. Organization is also available as a 'dimension' in FlexReports, using which you can slice and dice data, segregated based on immediate (one level down) child/sub orgs of the organization in-context. Based on role permissions, you can also switch the organization using the organization switcher, and will be able to use FlexReports to query data across FlexOrgs hierarchies.

Reducing AWS API Calls

At CloudHealth, we love to make optimizations in our existing code as much as we love to develop new features. One area of optimization that we have been thinking about is the consumption of AWS API quotas. To make sure that CloudHealth is not requesting empty responses from AWS via service APIs, our platform will now skip invoking service APIs if it detects that there are no charges for the service in your bill. Specifically, that means we will not collect assets from a service unless there are charges with $0 or more. This will not only reduce the consumption of your API quota but decrease your API costs too. Since the AWS inventory collection will now be dependent on the bill drops, the platform will not run collection for a service you just started using until after the first bill drop containing that data. Therefore, the initial collection of inventory may take up to 24 hours. Subsequent collection cycles will run at the same frequency as they do today.

Learn more about AWS asset collection frequency in this Help Center article.