ECS Sidecar
Installing the Asserts ECS sidecar container
The ECS sidecar container needs to be included in the task definition of each ECS Task. Here is a sample JSON excerpt of the sidecar container definition that can be added to your existing task definition JSON.
The ECS Sidecar can operate in two modes
Active Mode
In the Active
mode, the sidecar will gather container level metrics for CPU, Memory and Network bytes and remote write the metrics to a Prometheus TSDB. In the above example, the remote write URL and credentials for the Prometheus TSDB are provided. The Active
mode requires that the ECS Task IAM role should have the following permissions
Passive Mode
In the Passive
mode, the sidecar will gather container level metrics for CPU, Memory and Network bytes. But it will need to be scraped by the AWS Exporter. If the environment variables that begin with remoteWrite_
are removed, the exporter will default to Passive
mode
Last updated