Finally, you can export this query to a monitor so that you can be alerted whenever a threshold volume (defined in absolute or relative terms) of these packet loss events is reached.ĭatadog can also help you use VPC Flow Logs for Transit Gateway to troubleshoot network performance issues related to traffic surges. You can then filter or group by specific attachments, sources, or destinations, which could surface an issue with communication between (for example) AWS and your on-premises networks.

network.packets_lost.ttl_expired: Packets lost due to time to live (TTL) expiryīy using Datadog’s Log Explorer, you can easily create a log search for one or more of these packet loss types.

network.packets_lost.mtu_exceeded: Packets lost from packet size exceeding the maximum transmission unit (MTU).

network.packets_lost.black_hole: Packets being silently dropped by the destination.

network.packets_lost.no_route: Packets lost because of a missing route.

VPC Flow Logs for Transit Gateway provide information about the causes of this packet loss, such as: In this post, we’ll show you how integrating VPC Flow Logs for Transit Gateway into Datadog can help you to:ĭatadog Log Management helps you analyze your Transit Gateway flow logs so that you can more easily identify and troubleshoot network issues that are impacting performance.įor example, packet loss can sometimes occur when you deploy applications that span multiple VPCs or cloud and on-prem networks. The integration uses Datadog’s Lambda Forwarder to push logs to Datadog from an AWS CloudWatch log group or AWS S3 Bucket, where the logs are first published. To support this launch, Datadog now provides an integration that makes it easy to ingest and analyze your VPC Flow Logs for Transit Gateway for a range of use cases. They can also provide key information useful for troubleshooting, such as the number of packets lost and the causes of that packet loss, along with all elements included in the flow-including VPCs, subnets, ENIs, availability zones, AWS services, and source/destination AWS accounts. Flow log records contain core information, such as the related attachment ID, the source/destination IPs and ports, flow direction, and the number of packets and bytes transferred. Each flow log record captures an IP traffic flow that occurs within an aggregation interval. VPC Flow Logs for Transit Gateway solve this problem because they enable you to capture traffic through any or all attachments of a Transit Gateway. This requirement made it difficult to troubleshoot in scenarios where Transit Gateway owners lacked access to the VPC Flow Logs-a common problem when different teams own VPCs in different AWS accounts.

Prior to these logs, network administrators had to use flow logs from multiple VPCs to gain visibility into their entire AWS network. Today, AWS announced support for VPC Flow Logs for Transit Gateway so that customers can easily get deep, end-to-end visibility into all the network traffic going through their Transit Gateways. It also improves security by ensuring that traffic between VPCs and Transit Gateways stays encrypted and avoids traveling over the public Internet. For AWS customers operating at global scale with many accounts and VPCs, AWS Transit Gateway greatly simplifies AWS networking architecture by eliminating the need to manage complex peering relationships and massive route tables. AWS Transit Gateway is a service that makes it easy to connect multiple Amazon Virtual Private Clouds (VPCs), AWS accounts, AWS Regions, and on-premises networks together through a central hub.

Vpc flow logs