otelcol.receiver.awscloudwatch
EXPERIMENTAL: This is an experimental 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.levelflag toexperimental.
otelcol.receiver.awscloudwatch receives logs from Amazon CloudWatch and forwards them to other otelcol.* components.
Note
otelcol.receiver.awscloudwatchis a wrapper over the upstream OpenTelemetry Collectorawscloudwatchreceiver. Bug reports or feature requests will be redirected to the upstream repository, if necessary.
You can specify multiple otelcol.receiver.awscloudwatch components by giving them different labels.
Usage
otelcol.receiver.awscloudwatch "<LABEL>" {
region = "us-west-2"
output {
logs = [...]
}
}Arguments
You can use the following arguments with otelcol.receiver.awscloudwatch:
If imds_endpoint isn’t specified, and the environment variable AWS_EC2_METADATA_SERVICE_ENDPOINT has a value, it will be used as the IMDS endpoint.
Blocks
You can use the following blocks with otelcol.receiver.awscloudwatch:
output
RequiredThe output block configures a set of components to forward resulting telemetry data to.
The following arguments are supported:
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:
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_metricsonly applies tootelcol.exporter.*andotelcol.receiver.*components.
logs
The logs block configures how logs are collected from CloudWatch.
The following arguments are supported:
The logs block supports the following blocks:
logs > groups
The groups block supports the following blocks:
The blocks autodiscover or named are mutually exclusive.
logs > groups > autodiscover
The autodiscover block configures automatic discovery of log groups.
The following arguments are supported:
The autodiscover block supports the following blocks:
logs > groups > autodiscover > streams
The streams block configures filtering of log streams for the autodiscovered log groups.
The following arguments are supported:
logs > groups > named
The named block explicitly configures specific log groups to collect from. Multiple named blocks can be specified.
The following arguments are supported:
Exported fields
otelcol.receiver.awscloudwatch doesn’t export any fields.
Component health
otelcol.receiver.awscloudwatch is only reported as unhealthy if given an invalid configuration.
Debug information
otelcol.receiver.awscloudwatch doesn’t expose any component-specific debug information.
Example
The following example collects logs from specific EKS cluster log groups and forwards them through a batch processor:
otelcol.receiver.awscloudwatch "default" {
region = "us-west-2"
logs {
poll_interval = "3m"
max_events_per_request = 5000
groups {
named {
group_name = "/aws/eks/dev-cluster/cluster"
names = ["api-gateway"]
}
named {
group_name = "/aws/eks/prod-cluster/cluster"
prefixes = ["app-", "service-"]
}
}
}
output {
logs = [otelcol.processor.batch.default.input]
}
}
otelcol.processor.batch "default" {
output {
logs = [otelcol.exporter.otlp.default.input]
}
}
otelcol.exporter.otlp "default" {
client {
endpoint = env("<OTLP_ENDPOINT>")
}
}Compatible components
otelcol.receiver.awscloudwatch can accept arguments from the following components:
- Components that export OpenTelemetry
otelcol.Consumer
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.



