Use the instructions below to enable metric collection for the AWS App Mesh proxy sidecar, called Envoy. Users can choose to add sidecars in one of three modes: deploying, patching the deployment later, or using the AWS App Mesh injector controller. All modes are supported by the following steps.
Alternatively, the appmesh injector can be deployed by following the App Mesh with EKS documentation using the option enable-datadog-tracing=true or environment variable ENABLE_DATADOG_TRACING=true.
Prerequisite: Add Datadog Agents to each of your Fargate task definitions with App Mesh enabled, such as an Envoy sidecar injected, using the ECS Fargate integration documentation.
Due to limitations in App Mesh, forwarding metrics from an ECS task to Datadog requires the Egress filter to be set to Allow External Traffic.
Update all task definitions containing the Envoy sidecar and Datadog Agent with the following Docker labels. See Integration Setup for ECS Fargate for details.
Set the AWS App Mesh parameters ENABLE_ENVOY_DATADOG_TRACING and DATADOG_TRACER_PORT as environment variables in the ECS Fargate task definition. Learn more in the AWS App Mesh documentation.
Prerequisite: Add Datadog Agents to each of your ECS EC2 task definitions with App Mesh enabled, such as an Envoy sidecar injected, using the ECS integration documentation.
Due to limitations in App Mesh, forwarding metrics from an ECS task to Datadog requires the Egress filter to be set to Allow External Traffic.
Update all task definitions containing the Envoy sidecar and Datadog Agent with the following Docker labels. See Integration Setup for ECS Fargate for details.
Enable trace collection with the instructions in the ECS integration documentation.
Set the AWS App Mesh parameters ENABLE_ENVOY_DATADOG_TRACING and DATADOG_TRACER_PORT as environment variables in the ECS task definition. Learn more in the AWS App Mesh documentation.