Querying VPC Flow Logs
Function
This API is used to query all VPC flow logs of the tenant submitting the request. The VPC flow logs are filtered based on the filtering condition.
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 the required permissions in Permissions and Supported Actions.
- If you are using identity policy-based authorization, the following identity policy-based permissions are required.
Action
Access Level
Resource Type (*: required)
Condition Key
Alias
Dependencies
vpc:flowLogs:list
List
flowLog *
-
vpc:flowLogs:get
-
URI
GET /v1/{project_id}/fl/flow_logs
Example:
GET https://{Endpoint}/v1/b2782e6708b8475c993e6064bc456bf8/fl/flow_logs?name=flowlog
Table 1 describes the parameters.
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
project_id |
Yes |
String |
|
|
id |
No |
String |
|
|
name |
No |
String |
|
|
tenant_id |
No |
String |
|
|
description |
No |
String |
|
|
resource_type |
No |
String |
|
|
resource_id |
No |
String |
|
|
traffic_type |
No |
String |
|
|
log_group_id |
No |
String |
|
|
log_topic_id |
No |
String |
|
|
log_store_type |
No |
String |
|
|
status |
No |
String |
Flow log status
|
|
limit |
No |
Integer |
Specifies the number of records that will be returned on each page. The value is from 0 to 2000. The default value is 2000. limit can be used together with marker. For details, see the parameter description of marker. |
|
marker |
No |
String |
Specifies a resource ID for pagination query, indicating that the query starts from the next record of the specified resource ID. This parameter can work together with the parameter limit.
|
Request Parameters
None
Example Request
GET https://{Endpoint}/v1/b2782e6708b8475c993e6064bc456bf8/fl/flow_logs?name=flowlog
Response Parameters
|
Parameter |
Type |
Description |
|---|---|---|
|
flow_logs |
Array of FlowLog objects |
FlowLog object list. For details, see Table 3. |
|
Parameter |
Type |
Description |
|---|---|---|
|
id |
String |
|
|
name |
String |
|
|
tenant_id |
String |
|
|
description |
String |
|
|
resource_type |
String |
|
|
resource_id |
String |
|
|
traffic_type |
String |
|
|
log_group_id |
String |
|
|
log_topic_id |
String |
|
|
log_store_type |
String |
|
|
admin_state |
Boolean |
|
|
status |
String |
|
|
created_at |
String |
|
|
updated_at |
String |
|
Example Response
{
"flow_logs": [
{
"id": "35868d55-443e-4d5c-90a4-ac618dc45c1a",
"name": "flowlog",
"description": "just a test",
"tenant_id": "b2782e6708b8475c993e6064bc456bf8",
"resource_type": "port",
"resource_id": "05c4052d-8d14-488f-aa00-19fea5a25fde",
"traffic_type": "reject",
"log_group_id": "05c4052d-8d14-488f-aa00-19fea5a25fff",
"log_topic_id": "a9d7dee7-37d2-4cba-a208-a016252aaa63",
"log_store_type": "lts",
"created_at": "2019-01-14T11:03:02",
"updated_at": "2019-01-14T11:03:02",
"status": "ACTIVE",
"admin_state": true
}
]
}
Status Code
See Status Codes.
Error Code
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank 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