Locale selector icon
Sep202010

Uploading Azure Partner Detailed Bills to S3

We have released the ability for CloudHealth to automatically upload your Azure Billing Records to an Amazon S3 bucket. Once enabled, CloudHealth will upload the Azure Detailed Bill for both classic CSP and Azure Plan to the specified S3 bucket twice per day.

To opt-in to this feature, you’ll need to go to the Admin > Settings menu at the Partner tenant level and update the setting “Upload Azure Billing Records to Bill Generation S3 Bucket” to “On”.

FlexOrgs Local and Shared Perspectives for AWS - Private Beta

We’re pleased to announce the private beta for FlexOrgs Local and Shared Perspectives for AWS. This release unlocks the power of Perspective creation at all levels of your FlexOrgs hierarchy for AWS. Members of subOrganizations can manage their own subset of Perspectives that are contextually relevant to them. 

If you’re interested in participating in the private beta, please contact your CloudHealth Technical Account Manager to learn more and determine eligibility.

Updates to Kubernetes Reporting - Coming Soon

We have been working on significant improvements to the underlying technology of our containers reporting and 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 today). 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. CPU and Memory requests, also used by containers cost distribution, will no longer be labeled “Used CPU” and “Used Memory” but rather “Requested CPU” and “Requested Memory.”

    • 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 plans to automatically generate new saved reports and subscriptions to replace your current ones, but these may require some minor adjustments given the nature of the terminology and configuration changes.

  • Improvements to data aggregation.

We plan to roll out these Kubernetes improvements in the coming weeks, with similar improvements to follow for ECS reports. Stay tuned for more updates. 

AWS Savings Plan Policies

To help you stay on top of your savings mechanisms and avoid a case where one unexpectedly expires, you can now configure policies to alert on and/or take action regarding expiring AWS Savings Plans.

You can also enforce tagging governance with policies that catch untagged or mistagged Savings Plans.

Azure Cost and Usage Report Improvements

We recently released a number of improvements to our Azure cost and usage reports that result in these reports being 6 to 8 hours fresher. This means that as of last week, customers configured with an EA, PAYG, or direct Microsoft Commerce Agreement, should see more than twice as much data for the prior day (EDT) as they did before for all cost and usage reports.