Additional details of the maintenance in the form of json.
These are alternative actions to the requested instanceAction that can be taken to resolve the Maintenance.
For Instances that have local storage, this field is set to true when local storage will be deleted as a result of the Maintenance.
Indicates if this MaintenanceEvent is capable of being rescheduled up to the timeHardDueDate.
The OCID of the compartment that contains the instance.
A unique identifier that will group Instances that have a relationship with one another and must be scheduled together for the Maintenance to proceed. Any Instances that have a relationship with one another from a Maintenance perspective will have a matching correlationToken.
The creator of the maintenance event.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
Example: {@code {\"Operations\": {\"CostCenter\": \"42\"}}}
It is the descriptive information about the maintenance taking place on the customer instance.
A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
This is the estimated duration of the Maintenance, once the Maintenance has entered the STARTED state.
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags.
Example: {@code {\"Department\": \"Finance\"}}
The OCID of the maintenance event.
This is the action that will be performed on the Instance by OCI when the Maintenance begins.
The OCID of the instance.
Provides more details about the state of the maintenance event.
The current state of the maintenance event.
This indicates the priority and allowed actions for this Maintenance. Higher priority forms of Maintenance have tighter restrictions and may not be rescheduled, while lower priority/severity Maintenance can be rescheduled, deferred, or even cancelled. Please see the Instance Maintenance documentation for details.
This is the reason that Maintenance is being performed. See Instance Maintenance documentation for details.
The duration of the time window Maintenance is scheduled to begin within.
The date and time the maintenance event was created, in the format defined by RFC3339. Example: {@code 2016-08-25T21:10:29.600Z}
The time at which the Maintenance actually finished.
It is the scheduled hard due date and time of the maintenance event. The maintenance event will happen at this time and the due date will not be extended.
The time at which the Maintenance actually started.
The beginning of the time window when Maintenance is scheduled to begin. The Maintenance will not begin before this time.
It is the event in which the maintenance action will be be performed on the customer instance on the scheduled date and time.