Update to Microsoft Azure VM Metrics Collection – Action Required

We have upgraded to a new version of the Azure Monitor API used to collect metrics about Azure Virtual Machines. The latest version of this API provides improved stability and resolves issues where metric data may have been previously incomplete. Instructions on how to configure the new collection policies can be found in this Help Center article. Please note that customers who have previously configured a collection policy for the older version of the Azure Monitor API will still need to update their configuration. We will continue to support the old API in parallel for the time being, with plans to deprecate the old API version in the near future.

Update to Kubernetes Resource Management

Today, we are announcing the addition of Resources Limits as measures in Kubernetes Resources and Kubernetes Allocation Reports in CloudHealth. The new measures are:

• CPU Limits

• CPU Limits Hours

• Memory Limit Hours

• Memory Limits (GB)

No action is required on your part to take advantage of these new measures in the report.

Learn more about container measures in this Help Center article and/or learn more about managing Kubernetes resources in this Kubernetes documentation.

Updates to CloudHealth Kubernetes Collector Agent

We are announcing significant updates to the CloudHealth Kubernetes Collector Agent. The new agent will be collecting additional information and usage metrics from the Kubernetes Metrics Server (if available) in your environment. The changelog has more information about the updates and additional information we are collecting. Please follow the instructions specific to the installation method you used to update the agent:

• Helm Chart: Please follow these instructions to update the chart.

• Manual Deployment: Setup -> Containers -> Select Any Cluster -> Follow instructions from “Collector Deployment Page”

Once you update to the latest agent and it can communicate with the Kubernetes metric server in your environment, the status will be reflected as “Active” within an hour. The status will be listed as “Inactive” if CloudHealth has not received usage data from the cluster after 2 hours.

Update to FlexReports Chart Preview

FlexReports "chart preview" now supports dual Y-axis. Dual Y-axis allows data from different datasets to be visualized together. It illustrates correlations between two different datasets with different magnitudes and helps interpret data more easily.

The screenshot below shows an example of dual Y-axis, where each dataset has a separate axis. BlendedCost is represented by Chart type & UnblendedCost is represented by Chart type dual Y-axis.