With some initial investigation, we would like to add support for monitoring AWS Fargate using Metricbeat. AWS ECS container agent injects an environment variable into each container, referred to as the task metadata endpoint which provides various task metadata and Docker stats to the container. We can collect monitoring metrics from each container inside the same task using this task metadata endpoint.

Since we can only get metrics from task metadata endpoint when running Metricbeat as a container in the Fargate task, there are no AWS credentials like access keys and secret access keys needed. This means awsfargate can be its own Metricbeat Module (instead of making it a metricset under aws module).

This issue is to track the work for adding awsfargate module into Metricbeat.

Metricbeat Module / Dataset release checklist

This checklist is intended for Devs which create or update a module to make sure modules are consistent.

Metricbeat module

• Example data.json exists and an automated way to generate it exists (go test -data)
• Test environment in Docker exist for integration tests