[receiver/awscontainerinsight] High cardinality with default configuration

[pjanotti]

Component(s)

receiver/awscontainerinsight

What happened?

Description

Enabling the receiver generates high cardinality metrics since, by default, it adds Timestamp to the published metrics resource.

Steps to Reproduce

Enable the receiver in an AWS ECS EC2 cluster.

Expected Result

No high cardinality metrics from enabling the receiver.

Actual Result

High cardinality metrics.

Collector version

v0.111.0

Environment information

Environment

OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")

OpenTelemetry Collector configuration

No response

Log output

No response

Additional context

The Timestamp may be useful for some post processing by some AWS service, however, per general recommendation on OTel high-cardinality metrics should be avoided on the default configuration, even if a workaround using the resource attribute processor is relatively easy. It seems to me that this attribute should be disabled by default and possibly enabled by some specific configuration.

[github-actions]

Pinging code owners:

• receiver/awscontainerinsight: @Aneurysm9 @pxaws

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/awscontainerinsight: @Aneurysm9 @pxaws

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[pxaws]

I would suggest to define some config or env variable to control the Timestamp field. For AWS Container Insights use cases, we don't have the so called high cardinality issue because Timestamp will be converted into a field in emf logs by aws emf exporter (in this repo). EMF logs has its own way to define the metrics schema (metric name, dimension, ...) and the Timestamp is just used for getting the time stamp.