Collecting Logs from ER
LTS can collect logs from Enterprise Router (ER). For details, see Creating a Flow Log.
This function is available only in regions AF-Johannesburg, AP-Singapore, CN-Hong Kong, CN East-Shanghai1, LA-Mexico City1, LA-Mexico City2, LA-Santiago, and LA-Sao Paulo1.
Structuring Template Details
- ER log example
Table 1 Structuring template example Template Name
Example Log
ER Enterprise Router
1 0ebc7f641d80f4d32f9dc0056bdaae5b 740cc7e2-c686-496e-9fae-2dfc33e9d443 2756dc58-49be-413d-852f-accc5657a6c3 192.168.3.227 172.16.0.206 0 0 1 279 27342 1670338595 1670339195 egress
- Structuring fields and description
Table 2 Structuring fields Field
Example
Description
Type
version
1
ER flow log version.
long
project_id
0ebc7f641d80f4d32f9dc0056bdaae5b
Project ID.
string
instance_id
740cc7e2-c686-496e-9fae-2dfc33e9d443
Enterprise router ID.
string
resource_id
2756dc58-49be-413d-852f-accc5657a6c3
ID of the attachment that the traffic is generated for.
string
srcaddr
192.168.3.227
Source IP address.
string
dstaddr
172.16.0.206
Destination IP address.
string
srcport
0
Source port.
long
dstport
0
Destination port.
long
protocol
1
Internet Assigned Numbers Authority (IANA) protocol number of the traffic.
For more information, see Assigned Internet Protocol Numbers.
long
packets
279
Number of data packets during the flow log capture.
long
bytes
27342
Size of the data packet during the flow log capture.
long
start
1670338595
The time when the capture started, in Unix seconds.
long
end
1670339195
The time when the capture ended, in Unix seconds.
long
direct
egress
Traffic direction:
- ingress: traffic going in to the attachment.
- egress: traffic going out of the attachment.
string
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
