- Release Notes
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Resource Management
- Log Collection
- Log Search
- Log Analysis
- Log Shipping
- Log Consumption
- Permission Management
- CAM Access Authorization
- Resource List
- Action List
- Granting a Sub-account Permissions for CLS
- Granting a Sub-account Full Permissions for CLS Resources
- Granting a Sub-account Read-only Permission for CLS Resources
- Granting a Sub-account Permissions for Embedded CLS Console
- Granting a Sub-account Full Permissions for a CLS Log Topic
- Granting a Sub-account Read-only Permission for a CLS Log Topic
- Granting a Sub-account Permissions to Collect Logs for a CLS Log Topic
- Monitoring Alarm
- Function Processing
- Developer Guide
- API Documentation
- Glossary
- FAQs
- Service Level Agreement
- Appendix
- Notices
- Release Notes
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Resource Management
- Log Collection
- Log Search
- Log Analysis
- Log Shipping
- Log Consumption
- Permission Management
- CAM Access Authorization
- Resource List
- Action List
- Granting a Sub-account Permissions for CLS
- Granting a Sub-account Full Permissions for CLS Resources
- Granting a Sub-account Read-only Permission for CLS Resources
- Granting a Sub-account Permissions for Embedded CLS Console
- Granting a Sub-account Full Permissions for a CLS Log Topic
- Granting a Sub-account Read-only Permission for a CLS Log Topic
- Granting a Sub-account Permissions to Collect Logs for a CLS Log Topic
- Monitoring Alarm
- Function Processing
- Developer Guide
- API Documentation
- Glossary
- FAQs
- Service Level Agreement
- Appendix
- Notices
Feature Description
This API is used to get the logset information list.
Request
Sample request
GET /logsets HTTP/1.1
Host: <Region>.cls.tencentyun.com
Authorization: <AuthorizationString>Request line
GET /logsetsRequest header
There are only common request headers but no special request headers.
Request parameters
None.
Response
Sample response
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 123
{
"logsets": [
{
"logset_id": "xxxx-xx-xx-xx-xxxxxxxx",
"logset_name": "testname",
"period": 15,
"create_time": "2017-08-08 12:12:12",
"assumer_uin": 1000088888,
"assumer_name": "xxxxxx",
"logset_modify_acl": 31
}
]
}Response header
There are only common response headers but no special response headers.
Response parameters
| Field Name | Type | Required | Description |
|---|---|---|---|
| logsets | JsonArray | Yes | Logset information array |
LogsetInfo is in the following format:
| Field Name | Type | Required | Description |
|---|---|---|---|
| logset_id | string | Yes | Logset ID |
| logset_name | string | Yes | Logset name |
| period | int | Yes | Retention period in days |
| create_time | string | No | Creation time |
| assumer_uin | uint64 | No | uin of the service that creates the logset (this field is present only when a general account views the logsets created by a service account) |
| assumer_name | string | No | Name of the service that creates the logset (this field is present only when a general account views the logsets created by a service account) |
| logset_modify_acl | int | No | General user's permission to modify logsets, i.e., modify_acl (0B00000: modification prohibited, 0B00001: modification allowed for basic information) (this field is present only when a general account views the logsets created by a service account) |
Error Codes
For more information, please see Error Codes.
Yes
No
Was this page helpful?