AWS Direct Connect

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Overview

This integration collects metrics from AWS Direct Connect, such as connection state, bit rate ingress and egress, packet rate ingress and egress, and more.

Setup

Installation

If you haven’t already, set up the Amazon Web Services integration first.

Metric collection

  1. In the AWS integration page, ensure that DirectConnect is enabled under the Metric Collection tab.

  2. Add those permissions to your Datadog IAM policy in order to collect AWS Direct Connect metrics:

    • directconnect:DescribeConnections: Used to list available Direct Connect connections.
    • directconnect:DescribeTags: Used to gather custom tags applied to Direct Connect connections.

    For more information, see the Direct Connect policies on the AWS website.

  3. Install the Datadog - AWS Direct Connect integration.

Log collection

Enable logging

Configure AWS Direct Connect to send logs either to a S3 bucket or to CloudWatch.

Note: If you log to a S3 bucket, make sure that amazon_directconnect is set as Target prefix.

Send logs to Datadog

  1. If you haven’t already, set up the Datadog Forwarder Lambda function.

  2. Once the Lambda function is installed, manually add a trigger on the S3 bucket or CloudWatch log group that contains your AWS Direct Connect logs in the AWS console:

Data Collected

Metrics

aws.dx.connection_bps_egress
(rate)
The bit rate for outbound data from the AWS side of the connection.
Shown as bit
aws.dx.connection_bps_ingress
(rate)
The bit rate for inbound data to the AWS side of the connection.
Shown as bit
aws.dx.connection_error_count
(count)
The total error count for all types of MAC level errors on the AWS device. The total includes cyclic redundancy check (CRC) errors.
Shown as error
aws.dx.connection_light_level_rx
(gauge)
Indicates the health of the fiber connection for ingress (inbound) traffic to the AWS side of the connection.
aws.dx.connection_light_level_tx
(gauge)
Indicates the health of the fiber connection for egress (outbound) traffic from the AWS side of the connection.
aws.dx.connection_pps_egress
(rate)
The packet rate for outbound data from the AWS side of the connection.
Shown as packet
aws.dx.connection_pps_ingress
(rate)
The packet rate for inbound data to the AWS side of the connection.
Shown as packet
aws.dx.connection_state
(gauge)
The state of the connection. 0 indicates DOWN and 1 indicates UP.
aws.dx.virtual_interface_bps_egress
(rate)
The bitrate for outbound data from the AWS side of the virtual interface.
Shown as bit
aws.dx.virtual_interface_bps_ingress
(rate)
The bitrate for inbound data to the AWS side of the virtual interface.
Shown as bit
aws.dx.virtual_interface_pps_egress
(rate)
The packet rate for outbound data from the AWS side of the virtual interface.
Shown as packet
aws.dx.virtual_interface_pps_ingress
(rate)
The packet rate for inbound data to the AWS side of the virtual interface.
Shown as packet

Each of the metrics retrieved from AWS are assigned the same tags that appear in the AWS console, including but not limited to host name, security-groups, and more.

Events

The AWS Direct Connect integration does not include any events.

Service Checks

The AWS Direct Connect integration does not include any service checks.

Troubleshooting

Need help? Contact Datadog support.

PREVIEWING: esther/docs-9518-update-example-control-sensitive-log-data