- Product Introduction
- Purchasing Guide
- Operation Guide
- Operations Overview
- Viewing ENI Information
- Creating an ENI
- Configuring Security Groups
- Binding and Configuring an ENI
- Setting Service Level
- Deleting an ENI
- Unbinding from a CVM
- Binding Secondary Private IP Addresses
- Releasing Secondary Private IP Addresses
- Binding EIPs
- Unbinding EIPs
- Modifying Primary Private IPs
- Changing the Subnet of an ENI
- Cloud Access Management
- Best Practice
- API Documentation
- FAQs
- Contact Us
- Glossary
- Product Introduction
- Purchasing Guide
- Operation Guide
- Operations Overview
- Viewing ENI Information
- Creating an ENI
- Configuring Security Groups
- Binding and Configuring an ENI
- Setting Service Level
- Deleting an ENI
- Unbinding from a CVM
- Binding Secondary Private IP Addresses
- Releasing Secondary Private IP Addresses
- Binding EIPs
- Unbinding EIPs
- Modifying Primary Private IPs
- Changing the Subnet of an ENI
- Cloud Access Management
- Best Practice
- API Documentation
- FAQs
- Contact Us
- Glossary
Flow Logs provides a full-time, full-flow and non-intrusive traffic collection service. It enables you to store and analyze the collected network traffic in real time for troubleshooting, compliance auditing, architecture optimization, and security detection.
You can create a flow log for an ENI to collect the inbound/outbound traffic. The collected traffic will be stored and analyzed in Tenceng Cloud CLS. This document describes how to create a flow log for an ENI.
Prerequisites
The CVM to which the ENI is bound is supported by Flow Logs. See Supported List.
You have granted permissions to FL to access CLS.
You have created a log topic. See Creating a Log Topic.
Sample Case
CVM A (10.16.0.22) and CVM B (10.16.0.40) reside in the same VPC. After you log in to the CVM A and run the
ping command to the CVM B, the ENIs on both CVMs will be triggered to generate traffic. If a flow log is created for the ENI on CVM A, the flow log also records the traffic.
Directions
1. Log in to the VPC console and select Flow Logs > Log List in the left sidebar.
2. In the upper-left corner of the Flow Logs page, choose the target region. Click + New and complete the configuration.
Field | Description |
Name | The name of the flow log. |
Collection range | This specifies the collection range of the flow log. Select "ENI" in this example. |
VPC | The VPC where the ENI resides. Select the VPC of CVM A in this example. |
Subnet | The subnet where the ENI resides. Select the subnet of CVM A in this example. |
Collection type | This specifies the type of traffic to be collected by the flow log: All traffic, or the traffic rejected or accepted by security groups or ACL. Select "Accept" in this example. |
Logset | This specifies the storage location in CLS for the flow log. Please select an existing logset. You can also click Create to add a logset in the CLS console. |
Log topic | This specifies the minimum dimension of log storage, which is used to distinguish log types, such as Accept log. You can go to the CLS console to add a log topic. |
Tag key | (Optional) It is used for locating and managing flow logs. You can create a tag key or select an existing one. |
Tag value | (Optional) You can create a tag value, select an existing one, or just leave it empty. |
3. Click OK.
Note:
For the first creation of a flow log, it takes about 10 minutes before you can see he logs in the CLS console.
The Flow Logs service is free of charge, but you need to pay for the data stored in CLS.
Result Validation
After 10 minutes, locate the flow log you’ve created on the Flow logs page and click View in the Operation column to access the Search and analysis page. Select a time range and search for the IP of the CVM B.
Yes
No
Was this page helpful?