Rules
Rules is a CCA feature that checks the resources used in the cloud, returning recommendations for optimizing the environment.
GCP Rules are Savings rules.
How to get to Rules:
In the CCA side feature menu, select Rules.

Filters
On the home screen it possible to search for available rules:

And filter by categories:

Report
When you click on “Download report”, a .csv file is downloaded with details of all the rules.

Rules
The CCA Rules are a set of recommendations based on the services available from the provider. For GCP, there is a category mentioned above.
For each rule, it is possible to view some information:

Monitored accounts: Lists the number of accounts that are being monitored for this recommendation.
Total resources found: Lists the number of resources that apply to the rule.
Total estimated savings: Estimated cost of savings with implementation of the recommendations.
Clicking on the rule name in blue opens a detailed breakdown of the rule, showing the following information:
Monitored accounts
Non-compliance resources
Total ignored resources found
Ignored resources cost
Total estimated savings

The system also allows you to filter by Account ID, Resource ID, or Region, as highlighted below:

Clicking on the option “Download report”, a .csv file is downloaded with details only for the selected rule.

Further down, the system presents some action options:

By clicking the ignore icon "
" you can ignore the recommendation for that selected resource. The system will display a screen to you explain the reason why you want to ignore the resource.

By describing the reason and confirming the action, clicking the checkbox, the system will enable the button to complete the action:

In the icon next to
" you can view details about the chosen resource such as resource information and Meta Data:

Rule settings
Clicking on the "" gear, opens the rule configuration.

In the configuration, you can search for the customization you want to view.

By clicking on the "" key corresponding to the customization, it is possible to open the rule customizations, allowing you to disable the rule chosen in “Status”.

Default Settings:
In default setting, it is possible to have the configuration specified for each resource as:
Non-compliance after: Number of days after which the resource begins to be considered non-compliant. Example: Infrequent users: after 15 days, it is considered non-compliant.
Regions: The regions that will be listed are the regions that are being monitored.

By clicking the Edit option, you can configure the acceptable period for the resource to be considered out of compliance.
The system will prompt you to fill in the following fields:
Filter period operator: Select from the available options
Less than: When you want the number of days for the resource to be considered out of compliance to be less than the specified number.
Greater than: When you want the number of days for the resource to be considered out of compliance to be greater than the specified number.
Filter period days: Specify the number of days for the rule to be considered out of compliance.

By clicking the save button, the system will complete the rule compliance customization.
If this rule has no customization, the compliance value will be as per the default values.
It is possible to add new customizations to the rule.

Clicking Add opens the customization screen, where you will need to fill in the following information:
Filter kind: Select between the two existing filter types
Filter only the resources that match the filter
Filter only the resources that do not match the filter
Filter key: Enter the filter key that matches the tag
Enter the filter value: Enter the value you want to return in the filter

After inserting the customizations you want, just click save, and the customization will be added to the selected rule.
Rules of Savings
SQL database without connections: Check if there are SQL databases without a connection longer than the specified period.
Low Use VM: This rule identifies GCP Virtual Machines (VMs) that are currently running but show consistently low CPU usage and low network output over a configurable time period. By querying GCP metrics, it determines which VMs are underutilized, helping teams to identify cost optimization opportunities by resizing, stopping, or decommissioning low-use VMs.
Unused custom image: Identifies custom images on GCP that are not being used, that is, they are not attached to any disk or instance template. These images may be generating unexpected costs.
Snapshots high retention: Identify snapshots retained for a long period of storage.
IPs detached: Public IPs not associated with a VM.
Stopped VM: Identifies stopped and unused VMs in GCP account
Last updated