dadrobna/enterprise-router
1
0
Fork 0
forked from docs/enterprise-router
Code Pull Requests Activity
enterprise-router/umn/source/flow_logs/flow_log_overview.rst
proposalbot 5f54580f4f Changes to er_umn from docs/doc-exports#680 (ER UMN 20230324 version 
first uplo

Reviewed-by: Sarda, Priya <prsarda@noreply.gitea.eco.tsi-dev.otc-service.com>
Co-authored-by: proposalbot <proposalbot@otc-service.com>
Co-committed-by: proposalbot <proposalbot@otc-service.com>
2023-12-06 13:27:37 +00:00

1.3 KiB
Raw Permalink Blame History

original_name

er_01_0108.html

Flow Log Overview

What Is a Flow Log?

Log Tank Service (LTS) can record flow logs for enterprise routers. A flow log records traffic of attachments on enterprise routers in real time. These logs allow you to monitor the network traffic of attachments and analyze network attacks, improving your O&M efficiency.

Flow logs can capture traffic of the following types of attachments:

  • VPC
  • Virtual gateway

Creation Process

Before creating a flow log for an enterprise router, you need to create a log group and a log stream on the LTS console.

Figure 1 Process of creating a flow log

Notes and Constraints

  • By default, you can create a maximum of 20 flow logs.
  • For TCP and UDP fragments, flow logs can record only the first fragment. Other fragments cannot be recorded because of incomplete packet header.
  • Flow logs can only record traffic generated for network communications and do not capture traffic generated by the network. For example, BGP traffic used by an enterprise router to learn routes of attachments is not recorded.