The unique OCID associated with the category.
The OCID of the compartment.
The name assigned to the compartment.
The estimated cost savings, in dollars, for the resource action. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
Additional metadata key/value pairs that you provide. They serve the same purpose and functionality as fields in the {@code metadata} object.
They are distinguished from {@code metadata} fields in that these can be nested JSON objects (whereas {@code metadata} fields are string/string maps only).
For example:
{@code {\"CurrentShape\": {\"name\":\"VM.Standard2.16\"}, \"RecommendedShape\": {\"name\":\"VM.Standard2.8\"}}}
The unique OCID associated with the recommendation history.
The recommendation history's current state.
Custom metadata key/value pairs for the resource action.
*Metadata Example**
\"metadata\" : { \"cpuRecommendedShape\": \"VM.Standard1.1\", \"computeMemoryUtilization\": \"26.05734124418388\", \"currentShape\": \"VM.Standard1.2\", \"instanceRecommendedShape\": \"VM.Standard1.1\", \"computeCpuUtilization\": \"7.930035319720132\", \"memoryRecommendedShape\": \"None\" }
The name assigned to the resource.
The unique OCID associated with the recommendation.
The name assigned to the recommendation.
The unique OCID associated with the resource action.
The unique OCID associated with the resource.
The kind of resource.
The current status of the resource action.
The date and time the recommendation history was created, in the format defined by RFC3339.
The metadata associated with the recommendation history and its related resources.