Analysis: GCP Recommendations
Analysis: GCP Recommendations
#340500
Description
For each instance recommendation, you can also download a PDF version of the Impact Analysis and Recommendation Report, which details system impact based on the recommendations. This report is useful to application owners who need to review recommended changes to their application resources. See the rptHref resource element for details on how to download this report.
To return a collection of all instances included in a GCP optimization analysis, see Analysis: GCP Systems.
Resource
/analysis/cloud/gcp/<analysisId>/results
Supported Operations
Table: GCP Recommendations Supported Operations
HTTP Method |
Input |
Output |
Description |
Path Parameter: Query String Parameter Options: Accept:
|
Collection of (JSON):
|
Returns a collection of recommendations for a GCP analysis. Specify application/json in the request header for returned recommendations in JSON format. Note: The returned recommendations can be in either JSON or Terraform-map format. Example: Returning GCP Instances with Downsize Recommendations |
|
GET /analysis/cloud/gcp/ <analysisId>/results |
Path Parameter: Query String Parameter Options: Accept:
|
Collection of (Terraform-map):
|
Returns a collection of recommendations for a GCP analysis in Terraform-map form. Specify application/terraform-map in the request header. Note: The returned recommendations can be in either JSON or Terraform-map format. Example: Returning GCP Recommendations with Low Effort in Terraform-map Form |
Table: GCP Recommendations Path Parameters
Parameter Name |
Type |
Description |
string |
The unique referenced ID of the GCP analysis. When the account grouping feature is enabled and you are working through the Densify API, with the cloud accounts that are part of a group, the workspace ID is replaced by the grouped account's primary key or a unique value that is used as the analysisId or as the ID in the href, that is used to obtain the Impact Analysis and Recommendation Report. |
Table: GCP Recommendation Query String Parameters
Parameter Name |
Type |
Description |
string |
You can use element filters to return a targeted subset of the recommendations. See the "F" (filter) designation in the Response schema table for a list of elements that support filtering. Refer to Filters for a complete description of this common operation. Usage example: ../results?recommendationType=Upsize |
|
|
Indicate whether or not to return system attributes:
Usage example: ../results?includeAttributes=true |
|
string |
Allows you to indicate which workload type data collection detail to return for the system. See dataQuality for the returned details. Specify a quoted list of workload type names for which data to be returned, separated by commas. Usage example: ../results?dataQuality="CPU Utilization (CINT2006 Rate),Memory Utilization in Percent" Note: A "400-Bad Request" error message is returned if a non-supported workload type is specified. |
Table: GCP Recommendations Response Schema
Element |
Type |
Filter/Sort |
Description |
string |
F |
The Densify assigned entity ID of the cloud system. |
|
string |
F |
The GCP identifier assigned to the Compute Engine system . |
|
string |
F |
The GCP Project identifier. |
|
string |
F |
The current instance type of the Compute Engine system. |
|
string |
F |
The recommended action for the system. This is also known as the Optimization Type in the Densify Console The following types of recommended actions are supported for this cloud platform:
Systems with insufficient information for analysis do not have a recommendation and are returned with limited elements. See Example: Returning GCP Systems with No Recommendations. |
|
string |
F |
The recommended instance type after Densify optimization analysis. |
|
string |
F |
[Self Optimization|Manual|N/A] Specifies whether this system is configured for Self-Optimization or Manual actioning based on the recommended action (recommendationType) and on the Self-Optimizing Automation policies. |
|
percentage |
|
The predicted uptime (%) for the system is based on the percentage of hours CPU utilization data is present in the workload range specified in the policy settings. Predicted uptime % for new systems started mid-way within the workload range is calculated from the time/date that the system was started, as opposed to the beginning of the interval resulting, in more accurate prediction for the future. |
|
string |
F |
The GCP name assigned to the system. |
|
string |
|
The reference resource to the Impact Analysis and Recommendation Report (also known as the Impact Analysis and Recommendation Report report). Use this reference to downoad the report. This report for the specified instance is available for download after the reporting database tables have been updated (i.e. after RDB populate has been executed). By default, the reporting database tables are updated once every night. You need to use the following in the request header to download the PDF file: Note: HTTPS must be enabled to download the Impact Analysis and Recommendation Report PDF. See Example: Downloading an Impact Analysis and Recommendation Report |
|
string |
F |
The approval setting for the system recommendation. The value in this string is derived from the Self-Optimizing Automation policies in implementationMethod and the approval attribute attr_ApprovalSetting. Possible settings include:
|
|
string |
F |
The Densify policy used for optimization analysis. |
|
string |
|
The value of savingestimate output parameter is the difference between the current and recommended instance type cost (this is the catalog cost). When using the API, the predicted uptime is NOT taken into consideration (i.e. [currentCost – recommendedCost]). The Impact Analysis and Recommendation Report report uses the predicted uptime % when calculating estimated savings regardless of whether the report is obtained through the UI or via API. |
|
string |
F |
[Moderate|Low|Very Low|None|Impossible] This element describes the effort required to investigate and implement the Densify recommendations. Effort for each system is calculated by rule-driven analytics based on factors (such as instance family change, storage change, data quality checks, feature changes, etc.) that can be configured in the policy settings and rule sets which capture best practices. "Impossible" effort is a result of a manual override for the instance. If a system is not ‘Not Analyzed’, Densify does not return an effortEstimate. Note: When using the Subscription API, Densify returns an effortEstimate of "impossible" for systems that are ‘Not Analyzed’. |
|
string |
F |
The power state of the system. |
|
string |
F |
The Densify entity ID of the catalog instance for the recommended instance type. |
|
string |
|
The cost of the existing instance type (i.e. the instance catalog cost). |
|
string |
|
The cost of the recommended instance type (i.e. the instance catalog cost) after Densify optimization analysis. |
|
string |
F |
The GCP service type:
|
|
string |
|
The hourly rate for the current instance type (i.e. instance catalog cost / monthly hours). This value is rounded to the nearest penny. |
|
string |
|
The hourly rate for the recommended instance type (i.e. instance catalog cost / monthly hours). This value is rounded to the nearest penny. |
|
array of
|
|
System attributes are properties set during the data collection process by a vendor platform (i.e. GCP) or by Densify for analytics. Note: The attribute array is only returned when includeAttributes=true is added to the query string. |
|
string |
|
This element is used to identify the terraform-map recommendations for a unique system and corresponds to the "Provisioning Id" GCP user-defined label value. The "Provisioning Id" label is used to uniquely identify a system, since its resourceId or system name could possibly change after an instance type update. See Example: Returning GCP Recommendations with Low Effort in Terraform-map Form. If the "Provisioning Id" label value is not set, then the system name is used to identify the recommendations. |
|
Unix time (in milliseconds) |
|
The first date and time the recommended instance type (i.e. the recommendedType element) was provided by Densify (Unix Epoch time, in milliseconds). |
|
Unix time |
|
The latest date and time the recommended instance type (i.e. the recommendedType element) was provided by Densify (Unix Epoch time, in milliseconds). |
|
integer |
|
The number of times Densify suggested the recommended instance type (i.e. the recommendedType element). This is the count of Densify analysis processes which produced the same recommended instance type from recommFirstSeen to recommLastSeen. This value is updated when the RDB populate task (i.e. the reporting database update process) is executed. The RDB populate task compares the current recommendedType with the new recommendedType to update the recommSeenCount counter. Note: In typical production environments, where the RDB populate task is scheduled to run once daily post data collection and analysis, the recommSeenCount value will reflect exactly the number of times the recommended instance type was provided. If your environment executes the RDB populate task more than once daily, the recommSeenCount value will be inflated beyond the actual number of times the instance type was recommended. Contact [email protected] if you have concerns about the recommSeenCount value. |
|
|
|
The following system data collection details are returned:
The following system workload collection details, for the last 30 days, are returned:
Note: If no workload data is collected for the system in the last 30 days, then the workloadDataLast30 element block is not returned. Note: The values in auditInfo are updated once a day, after the data collection and RDB populate processes are complete (i.e. the reporting tables have been updated with latest data collected). |
|
array of:
|
|
The dataQuality array provides workload type data collection details for the system:
Note: The dataQuality array is only returned when the dataQuality query string is specified in the request. In addition, if you specify a workload type in the request, for which system workload data does not exist in Densify, then no data is returned. Note: The values in the dataQuality array are updated after data collection and subsequent updates to the reporting tables (i.e. RDB Populate process) are completed. See Example: Returning GCP Instances with Downsize Recommendations. |
Examples
Example: Returning GCP Instances with Downsize Recommendations
The following example shows you how to return a collection of GCP instances with "Downsize" recommendations. In addition, this example also returns the "Disk I/O Bytes" workload data collection timestamps.

Request:
GET /analysis/cloud/gcp/d230c31d-13ac-543f-892e-2a35c8a3f232/results?recommendationType=Downsize&dataQuality="Disk I/O Bytes"
Response:
[
{
"entityId": "1679679b-9726-4a6b-9c33-a00f9261b6c1",
"resourceId": "4090409965214718888",
"accountIdRef": "east-prod-gidz",
"currentType": "n1-standard-8",
"recommendationType": "Downsize",
"recommendedType": "n1-standard-4",
"implementationMethod": "Self Optimization",
"predictedUptime": 13.82,
"totalHoursRunning": 230,
"name": "gl04.doop_xtr-32",
"rptHref": "/systems/1679679b-9726-4a6b-9c33-a00f9261b6c1/analysis-report",
"approvalType": "na",
"densifyPolicy": "GCP-Assess-Prod",
"savingsEstimate": 132.91621,
"effortEstimate": "Very Low",
"powerState": "Running",
"recommendedHostEntityId": "4e8309c5-cf70-42d9-ab70-4aa46516ff62",
"currentCost": 277.4,
"recommendedCost": 138.16,
"serviceType": "Compute Engine",
"currentHourlyRate": 0.38,
"recommendedHourlyRate": 0.24,
"recommFirstSeen": 1579680587570,
"recommLastSeen": 1589008760110,
"recommSeenCount": 24,
"auditInfo": {
"dataCollection": {
"dateFirstAudited": 1571951513223,
"dateLastAudited": 1588997765350,
"auditCount": 101
},
"workloadDataLast30": {
"firstDate": 1587009600000,
"lastDate": 1588910400000,
"totalDays": 23,
"seenDays": 5
}
},
"dataQuality": [
{
"workloadName": "Disk I/O Bytes",
"firstSeen": 1569297600000,
"lastSeen": 1588910400000,
"completeDays": 116,
"partialDays": 0
}
]
},
...
]
Example: Returning GCP Recommendations with Low Effort in Terraform-map Form
The following example shows you how to return a collection of recommendations with Low effort in terraform-map form. The label of each recommendation (i.e. "gl02.camp_gas-340", "gl02.camp_gas-432" in the example below) is the provisioningId element: "Provisioning Id" GCP label or system name value.

Request:
GET /analysis/cloud/gcp/d230c31d-13ac-543f-892e-2a35c8a3f232/results?effortEstimate=Low
Headers:
Accept: application/terraform-map
Authorization: Bearer <apiToken>
Response:
densify_recommendations = {
"gl02.camp_gas-340" = {
currentType = "n1-standard-8"
recommendedType = "n1-highmem-4"
approvalType = "na"
predictedUptime = "64.01"
recommendationType = "Downsize - Optimal Family"
powerState = "Running"
implementationMethod = "Manual"
savingsEstimate = "98.27805"
effortEstimate = "Low"
densifyPolicy = "GCP-Assess-Prod"
}
"gl02.camp_gas-432" = {
currentType = "n1-standard-8"
recommendedType = "n1-highmem-4"
approvalType = "na"
predictedUptime = "88.0"
recommendationType = "Downsize - Optimal Family"
powerState = "Running"
implementationMethod = "Manual"
savingsEstimate = "98.27805"
effortEstimate = "Low"
densifyPolicy = "GCP-Assess-Prod"
}
...
}
Example: Downloading an Impact Analysis and Recommendation Report
The following example shows you how to download a PDF Impact Analysis and Recommendation Report from the rptHref resource element provided in the instance recommendation output.
Note: HTTPS needs to be enabled to download the Impact Analysis and Recommendation Report PDF.
Example: Returning GCP Systems with No Recommendations
The following example shows you how to return a collection of GCP systems without recommendations. These systems typically do not have adequate data for optimization analysis and have the "Not Analyzed" designation in the recommendationType element.

Request:
GET /analysis/cloud/gcp/6b8ab8e1-a026-4db9-a4ae-2d684446731f/results?recommendationType=Not Analyzed
Headers:
Accept: application/json
Authorization: Bearer <apiToken>
Response:
[
{
"entityId": "1679679b-9726-4a6b-9c33-a00f9261b6c1",
"resourceId": "4090409723758657994",
"accountIdRef": "Prod9873318",
"currentType": "n1-standard-8",
"recommendationType": "Not Analyzed",
"name": "g105.doop_xtr-32",
"densifyPolicy": "GCP Assess",
"powerState": "Offline",
"currentCost": 27.47,
"serviceType": "Compute Engine",
"recommFirstSeen": 1579680587570,
"recommLastSeen": 1589008760110,
"recommSeenCount": 24,
"auditInfo": {
"dataCollection": {
"dateFirstAudited": 1571951513223,
"dateLastAudited": 1588997765350,
"auditCount": 101
}
}
},
...
]

Request:
GET /analysis/cloud/gcp/6b8ab8e1-a026-4db9-a4ae-2d684446731f/results?recommendationType=Not Analyzed
Headers:
Accept: application/terraform-map
Authorization: Bearer <apiToken>
Response:
densify_recommendations = {
"g105.doop_xtr-32" = {
currentType = "n1-standard-8"
recommendationType = "Not Analyzed"
powerState = "Offline"
densifyPolicy = "GCP Assess"
}
...
}