This is documentation for the next version of Grafana Alloy Documentation. For the latest stable release, go to the latest version.

Documentation Grafana Alloy Reference Components otelcol otelcol.receiver.awsecscontainermetrics

otelcol.receiver.awsecscontainermetrics

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.

This receiver supports ECS Fargate and ECS on EC2. It uses ECS Task Metadata Endpoint V4 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 receiver documentation for more details.

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

Usage

alloy Copy

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

Arguments

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

Blocks

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

output

debug_metrics

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

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.otlp.default.input]
  }
}

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

Compatible components

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

• Components that export OpenTelemetry otelcol.Consumer