AWS Transit Gateway monitoring integration

New Relic integrates with Amazon Web Services (AWS) for reporting your AWS Transit Gateway metrics and other data to New Relic.

This document explains how to activate the integration, and describes the data reported.

Features

Collect and send telemetry data to New Relic from your AWS Transit Gateway services using our integration. Monitor your services, query incoming data, and build dashboards to observe everything at a glance.

Activate integration

This integration is available through CloudWatch MetricStreams (Recommended).

To enable this integration, see how to connect AWS services to New Relic via CloudWatch Metric Streams.

Activate using the legacy API Polling integration

To enable this integration using our legacy polling integration, see how to enable the AWS API Polling integration.

Dica

You can change the polling frequency and filter data using configuration options.

Default polling information for the AWS Transit Gateway integration:

New Relic polling interval: 5 minutes
AWS CloudWatch data interval: 1 minute

Find and use data

To find your integration data, go to one.newrelic.com > All capabilities > Infrastructure > AWS and select an integration.

Data is attached to the following event type:

Entity	Event Type	Provider
TransitGateway	`AwsTransitGatewayTransitGatewaySample`	`AwsTransitGatewayTransitGateway`

For more on how to use your data, see Understand and use integration data.

Metric data

This integration collects AWS Transit Gateway data for TransitGateway.

Transit Gateway TransitGateway data

Metric	Unit	Description
`bytesIn`	Count	The number of bytes received by the transit gateway.
`bytesOut`	Count	The number of bytes sent from the transit gateway.
`packetsIn`	Count	The number of packets received by the transit gateway.
`packetsOut`	Count	The number of packets sent by the transit gateway.
`packetDropCountBlackhole`	Count	The number of packets dropped because they matched a blackhole route.
`packetDropCountNoRoute`	Count	The number of packets dropped because they did not match a route.
`bytesDropCountBlackhole`	Count	The number of bytes dropped because they matched a blackhole route.
`bytesDropCountNoRoute`	Count	The number of bytes dropped because they did not match a route.

Create alerts

You can set up to notify you if there are any changes. For example, you can set up an alert to notify relevant parties of critical or fatal errors.

Learn more about creating alerts here.