1. Home
  2. Analyze
  3. Cloud Utilization

Cloud Utilization

PyraCloud Utilization helps you track usage of your cloud resources. This enables you to determine whether certain resource need to be de-allocated or resized.

Exploring Utilization

To view resource utilization navigate to Analyze in the main navigation bar and click Utilization:

Figure 1 – Navigation to Cloud Utilization

This will open the utilization page and by default you will see three main sections:

  1. Search Bar
  2. Resource types selector
  3. List of resources
Figure 2 – Cloud Utilization Main Page

Searching

You can search by relevant resource properties and additionally, you can filter resources by recommendations (if applicable). For example, you can review all resources recommended for “shutdown” and see if utilization is low.

Resource Type Selector

Utilization currently support two resource types:

  1. Virtual Machines (that includes Azure scale sets)
  2. Storage accounts

Utilization supports both Azure and Amazon resource in one single unified view.

List of Resource

On the main page you will see a table with a list of your cloud resources with the main metric selected – for Virtual Machines it is Average CPU, and for Storage Accounts it is Capacity.

The table can be sorted by “all visible columns” so you can optimize your analysis.

Resource Details

The core feature of utilization is plotting metrics. You can navigate to details by clicking “View” on the list.

Figure 3 – Resource Details

The page contains four main areas:

  1. Resource Basic Information
  2. Date Range Selector
  3. Metric Selector
  4. Chart Area

Resource Basic Information

This section contains information like group, subscription, provider and tags. Additionally you can navigate directly to recommendation or resource modules.

Date Selector

Currently there are two types of selectors – 30 days and 7 days (older data is automatically removed).

In “30 days” mode you see a daily aggregation chart (4) and in “7 days” chart you see hourly aggregation.

Metric Selector

This drop down allows you to view available metrics. The module currently support CPU and network traffic for Virtual Machines, and Capacity and Counters for storage accounts.

After selecting, the metric chart is adjusted automatically.

Chart Area

As well as plotting metrics data, the chart can also present scale set resources, so you can analyze multiple nodes running on scale set.

Figure 4 – Showing Scale Set Machine

By clicking on the legend (1) you can show / hide scale set nodes.

Configuring Alerts

The utilization module supports custom alerts, so you can setup notifications based on the low utilization of your machines, or over utilization of your storage accounts.

Figure 5 – Creating Alerts

To create alerts, complete your search and then select the Create Alert button.

Figure 6 – Virtual Machine Alerts

By default, the alert modal appears with Virtual Machine (CPU) notifications. You can configure notifications to be alerted if machine utilization (from your search criterial) drops bellow (10%, 20% or a custom percentage).

Figure 7 – Storage Alerts

You can also configure alerts based on capacity of the storage accounts. If it grows above a defined threshold you will then be notified.

Note: Alerts are generated once per day at 5AM UTC

Configuring AWS Access

If the utilization module is not able to pull utilization metrics, you will see the below popup message:

Figure 8 – Unable to pull utilization metrics for AWS

Utilization uses CloudWatch to pull metrics. If you see the above message, it means CloudWatch was not assigned to PyraCloudRole.

To fix this, open the AWS Console and navigate to IAM.

Figure 9 – AWS – IAM

Then locate PyraCloudRole:

Figure 10 – PyraCloud Role in IAM

In the role, open PyraCloud ReadOnlyPolicy.

Figure 11 – ReadOnlyPolicy

Then click Edit policy.

Figure 11 – Edit PyraCloud Policy

Next, switch to JSON view.

Figure 12 – JSON View of PyraCloud Policy

In the editor please add “cloudwatch:GetMetricStatistics” and click Review on the bottom of the page.

Figure 13 – AWS JSON Role List

In the review summary you should see CloudWatch permission on the list.

Figure 14 – AWS Policy Review

If everything is ok, click Save Changes.

You have to repeat the above for all linked accounts if you are using AWS Organizations.

Utilization synchronizes data every hour, so on the next sync your utilization metrics should be synchronized with PyraCloud.

Updated on June 18, 2021

Was this article helpful?

Related Articles