Querying All Log Settings
Function
Query all log settings.
Calling Method
For details, see Calling APIs.
Authorization Information
Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.
- If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.
- If you are using identity policy-based authorization, no identity policy-based permission required for calling this API.
URI
GET /v1/{project_id}/antiddos/lts-config
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| project_id | Yes | String | Project ID |
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| enterprise_project_id | Yes | String | Enterprise project ID. |
Request Parameters
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| X-Auth-Token | Yes | String | User token. It can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is the user token. |
| Content-Type | Yes | String | Content-Type request header. |
Response Parameters
Status code: 200
| Parameter | Type | Description |
|---|---|---|
| enabled | Boolean | Whether to enable logging. The options are as follows: |
| lts_id_info | lts_id_info object | Log information. |
Example Requests
None
Example Responses
Status code: 200
{
"enabled" : true,
"lts_id_info" : {
"lts_group_id" : "3f664a8c-53bd-4f77-922d-xxxxxxxxxxxx",
"lts_attack_stream_id" : "ea9ffec3-6fe4-4884-9dd0-xxxxxxxxxxxx"
}
} Status Codes
| Status Code | Description |
|---|---|
| 200 | Request succeeded. |
| 401 | Unauthorized |
| 403 | Forbidden |
| 404 | Not Found |
Error Codes
See Error Codes.
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot