Values_5.DescribeVolumeStatusResultSourceDescribes the status of the specified volumes. Volume status provides the result of the checks performed on your volumes to determine events that can impair the performance of your volumes. The performance of a volume can be affected if an issue occurs on the volume's underlying host. If the volume's underlying host experiences a power outage or system issue, after the system is restored, there could be data inconsistencies on the volume. Volume events notify you if this occurs. Volume actions notify you if any action needs to be taken in response to the event. The DescribeVolumeStatus operation provides the following information about the specified volumes: Status: Reflects the current status of the volume. The possible values are ok, impaired , warning, or insufficient-data. If all checks pass, the overall status of the volume is ok. If the check fails, the overall status is impaired. If the status is insufficient-data, then the checks might still be taking place on your volume at the time. We recommend that you retry the request. For more information about volume status, see Monitor the status of your volumes in the Amazon EBS User Guide. Events: Reflect the cause of a volume status and might require you to take action. For example, if your volume returns an impaired status, then the volume event might be potential-data-inconsistency. This means that your volume has been affected by an issue with the underlying host, has all I/O operations disabled, and might have inconsistent data. Actions: Reflect the actions you might have to take in response to an event. For example, if the status of the volume is impaired and the volume event shows potential-data-inconsistency, then the action shows enable-volume-io. This means that you may want to enable the I/O operations for the volume and then check the volume for data consistency. For more information, see Work with an impaired EBS volume. Volume status is based on the volume status checks, and does not reflect the volume state. Therefore, volume status does not indicate volumes in the error state (for example, when a volume is incapable of accepting I/O.) The order of the elements in the response, including those within nested structures, might vary. Applications should not assume the elements appear in a particular order.
type nonrec t = {nextToken : Values_0.String_.t option;The token to include in another request to get the next page of items. This value is null when there are no more items to return.
*)volumeStatuses : Values_3.VolumeStatusList.t option;Information about the status of the volumes.
*)}val error_of_json :
'a ->
Yojson.Safe.t ->
[> `Unknown_operation_error of 'a * string option ]val to_value :
t ->
[> `Structure of
(string
* [> `List of
[> `Structure of
(string
* [> `List of
[> `Structure of
(string
* [> `String of string
| `Timestamp of string ])
list ]
list
| `String of Values_0.String_.t
| `Structure of
(string
* [> `Boolean of bool
| `Enum of string
| `List of
[> `Structure of
(string
* [> `Enum of string | `String of string ])
list ]
list
| `Long of Values_0.Long.t
| `String of string ])
list ])
list ]
list
| `String of Values_0.String_.t ])
list ]