---
title: "otelcol.receiver.awsecscontainermetrics | Grafana Alloy documentation"
description: "Learn about otelcol.receiver.awsecscontainermetrics"
---

# `otelcol.receiver.awsecscontainermetrics`

> **EXPERIMENTAL**: This is an [experimental](/docs/release-life-cycle/) component. Experimental components are subject to frequent breaking changes, and may be removed with no equivalent replacement. To enable and use an experimental component, you must set the `stability.level` [flag](/docs/alloy/latest/reference/cli/run/) to `experimental`.

`otelcol.receiver.awsecscontainermetrics` reads AWS ECS task- and container-level metadata, and resource usage metrics such as CPU, memory, network, and disk, and forwards them to other `otelcol.*` components.

> Note
> 
> `otelcol.receiver.awsecscontainermetrics` is a wrapper over the upstream OpenTelemetry Collector [`awsecscontainermetrics`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.147.0/receiver/awsecscontainermetricsreceiver) receiver. Bug reports or feature requests will be redirected to the upstream repository, if necessary.

This receiver supports ECS Fargate and ECS on EC2. It uses [ECS Task Metadata Endpoint V4](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-metadata-endpoint-v4.html) which is automatically available within the task’s containers. Therefore, you should run the Alloy collector using this receiver as a sidecar within the task you want to monitor. Refer to the upstream [`awsecscontainermetrics`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.147.0/receiver/awsecscontainermetricsreceiver) receiver documentation for more details.

You can specify multiple `otelcol.receiver.awsecscontainermetrics` components by giving them different labels.

## Usage

Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```alloy
otelcol.receiver.awsecscontainermetrics "<LABEL>" {
  output {
    metrics = [...]
  }
}
```

## Arguments

You can use the following arguments with `otelcol.receiver.awsecscontainermetrics`:

Expand table

| Name                  | Type       | Description                                 | Default | Required |
|-----------------------|------------|---------------------------------------------|---------|----------|
| `collection_interval` | `duration` | How frequently to collect and emit metrics. | “20s”   | no       |

## Blocks

You can use the following blocks with `otelcol.receiver.awsecscontainermetrics`:

No valid configuration blocks found.

### `output`

Required

The `output` block configures a set of components to forward resulting telemetry data to.

The following arguments are supported:

Expand table

| Name      | Type                     | Description                           | Default | Required |
|-----------|--------------------------|---------------------------------------|---------|----------|
| `logs`    | `list(otelcol.Consumer)` | List of consumers to send logs to.    | `[]`    | no       |
| `metrics` | `list(otelcol.Consumer)` | List of consumers to send metrics to. | `[]`    | no       |
| `traces`  | `list(otelcol.Consumer)` | List of consumers to send traces to.  | `[]`    | no       |

You must specify the `output` block, but all its arguments are optional. By default, telemetry data is dropped. Configure the `metrics`, `logs`, and `traces` arguments accordingly to send telemetry data to other components.

### `debug_metrics`

The `debug_metrics` block configures the metrics that this component generates to monitor its state.

The following arguments are supported:

Expand table

| Name                               | Type      | Description                                          | Default | Required |
|------------------------------------|-----------|------------------------------------------------------|---------|----------|
| `disable_high_cardinality_metrics` | `boolean` | Whether to disable certain high cardinality metrics. | `true`  | no       |

`disable_high_cardinality_metrics` is the Alloy equivalent to the `telemetry.disableHighCardinalityMetrics` feature gate in the OpenTelemetry Collector. It removes attributes that could cause high cardinality metrics. For example, attributes with IP addresses and port numbers in metrics about HTTP and gRPC connections are removed.

> Note
> 
> If configured, `disable_high_cardinality_metrics` only applies to `otelcol.exporter.*` and `otelcol.receiver.*` components.

## Exported fields

`otelcol.receiver.awsecscontainermetrics` doesn’t export any fields.

## Component health

`otelcol.receiver.awsecscontainermetrics` is only reported as unhealthy if given an invalid configuration.

## Debug information

`otelcol.receiver.awsecscontainermetrics` doesn’t expose any component-specific debug information.

## Example

The following example collects eight task-level metrics from the 52 metrics available in an ECS task and forwards them to a filter processor.

Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```alloy
otelcol.receiver.awsecscontainermetrics "default" {
  collection_interval = "60s"

  output {
    metrics = [otelcol.processor.filter.default.input]
  }
}

otelcol.processor.filter "default" {
  error_mode = "ignore"

  metrics {
    metric = [
      string.join([
        `metric.name != "ecs.task.memory.reserved"`,
        `metric.name != "ecs.task.memory.utilized"`,
        `metric.name != "ecs.task.cpu.reserved"`,
        `metric.name != "ecs.task.cpu.utilized"`,
        `metric.name != "ecs.task.network.rate.rx"`,
        `metric.name != "ecs.task.network.rate.tx"`,
        `metric.name != "ecs.task.storage.read_bytes"`,
        `metric.name != "ecs.task.storage.write_bytes"`,
      ], " and "),
    ]
  }

  output {
    metrics = [otelcol.exporter.otlphttp.default.input]
  }
}

otelcol.exporter.otlphttp "default" {
  client {
    endpoint = env("<OTLP_ENDPOINT>")
  }
}
```

## Compatible components

`otelcol.receiver.awsecscontainermetrics` can accept arguments from the following components:

- Components that export [OpenTelemetry `otelcol.Consumer`](../../../compatibility/#opentelemetry-otelcolconsumer-exporters)

> Note
> 
> Connecting some components may not be sensible or components may require further configuration to make the connection work correctly. Refer to the linked documentation for more details.