Asset Fingerprint - Auto-Started Item Information
Function
This API is used to check auto-started items in asset fingerprints.
URI
GET /v5/{project_id}/asset/auto-launch/statistics
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| project_id | Yes | String | Project ID |
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| name | No | String | Auto-started item name |
| type | No | String | Auto-started item type
|
| enterprise_project_id | No | String | Enterprise project ID. To query all enterprise projects, set this parameter to all_granted_eps. |
| limit | No | Integer | Number of records displayed on each page. The default value is 10. |
| offset | No | Integer | Offset, which specifies the start position of the record to be returned. The value must be a number no less than 0. |
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 a token. |
Response Parameters
Status code: 200
| Parameter | Type | Description |
|---|---|---|
| total_num | Integer | Total number of auto-started items |
| data_list | Array of AutoLaunchStatisticsResponseInfo objects | List of auto-started item statistics |
| Parameter | Type | Description |
|---|---|---|
| name | String | Auto-started item name |
| type | String | Auto-started item type
|
| num | Integer | Indicates the number of servers of auto-started items. |
Example Requests
The first 10 auto-startup items are queried by default.
GET https://{endpoint}/v5/{project_id}/asset/auto-launch/statistics Example Responses
Status code: 200
Number of servers having the process
{
"total_num" : 1,
"data_list" : [ {
"name" : "S12hostguard",
"type" : "0",
"num" : 5
} ]
} Status Codes
| Status Code | Description |
|---|---|
| 200 | Number of servers having the process |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.