Queries the time configurations of O&M events.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request parameters

Parameter Type Required Example Description
Action String Yes DescribeActiveOperationMaintainConf

The operation that you want to perform. Set the value to DescribeActiveOperationMaintainConf.

RegionId String Yes cn-hangzhou

The region ID of the instances for which the requested O&M events are configured.

Response parameters

Parameter Type Example Description
RequestId String 1A586DCB-39A6-4050-81CC-C7BD4CCDB49F

The ID of the request.

Config Object

The information about the requested time configurations.

CreatedTime String 2021-08-11T10:08:27Z

The creation time of the O&M event. The time follows the ISO 8601 standard in the yyyy-MM-ddThh:mm:ssZ format. The time is displayed in UTC.

CycleTime String 1,2,3,4,5,6,7

The days on which the O&M events are executed every week.

CycleType String Week

The cyclical type of the O&M events.

MaintainEndTime String 04:00:00Z

The end time of the O&M event.

MaintainStartTime String 04:00:00Z

The start time of the O&M event.

ModifiedTime String 2021-08-11T10:08:27Z

The last modified time of the O&M event. The time follows the ISO 8601 standard in the yyyy-MM-ddThh:mm:ssZ format. The time is displayed in UTC.

Status Long 1

The status of the O&M events.

HasConfig Long 1

Indicates whether the O&M events are configured. Valid values:

  • 1: indicates that the O&M events are configured.
  • 0: indicates that the O&M events are not configured.

Examples

Sample requests

http(s)://[Endpoint]/?Action=DescribeActiveOperationMaintainConf
&RegionId=cn-hangzhou
&Common request parameters

Sample success responses

XML format

HTTP/1.1 200 OK
Content-Type:application/xml

<DescribeActiveOperationMaintainConfResponse>
    <RequestId>1A586DCB-39A6-4050-81CC-C7BD4CCDB49F</RequestId>
    <Config>
        <CreatedTime>2021-08-11T10:08:27Z</CreatedTime>
        <CycleTime>1,2,3,4,5,6,7</CycleTime>
        <CycleType>Week</CycleType>
        <MaintainEndTime>04:00:00Z</MaintainEndTime>
        <MaintainStartTime>04:00:00Z</MaintainStartTime>
        <ModifiedTime>2021-08-11T10:08:27Z</ModifiedTime>
        <Status>1</Status>
    </Config>
    <HasConfig>1</HasConfig>
</DescribeActiveOperationMaintainConfResponse>

JSON format

HTTP/1.1 200 OK
Content-Type:application/json

{
  "RequestId" : "1A586DCB-39A6-4050-81CC-C7BD4CCDB49F",
  "Config" : {
    "CreatedTime" : "2021-08-11T10:08:27Z",
    "CycleTime" : "1,2,3,4,5,6,7",
    "CycleType" : "Week",
    "MaintainEndTime" : "04:00:00Z",
    "MaintainStartTime" : "04:00:00Z",
    "ModifiedTime" : "2021-08-11T10:08:27Z",
    "Status" : 1
  },
  "HasConfig" : 1
}

Error codes

HttpCode Error code Error message Description
400 IdempotentParameterMismatch The request uses the same client token as a previous, but non-identical request. Do not reuse a client token with different requests, unless the requests are identical. The error message returned because the request uses the same token that is used by a non-identical request. Only identical requests can use the same client token.

For a list of error codes, visit the API Error Center.