Metrics for StatefulSet deployments cannot easily be aggregated together

[jbeemster]

Component(s)

receiver/awscontainerinsight

Is your feature request related to a problem? Please describe.

Currently all deployment types but StatefulSet expose the PodName as the name of the deployment itself (see: https://github.com/open-telemetry/opentelemetry-collector-contrib/blame/main/receiver/awscontainerinsightreceiver/internal/stores/podstore.go#L590-L597).

We have started exploring using StatefulSet's and this difference means we cannot easily set alarms or dashboards against the aggregate metric view as each PodName value is unique rather than consistent across the pool of pods being used. For example being able to set a general alarm against the CPU utilization of the entire pool of auto-scaling pods in use.

Describe the solution you'd like

Ideally I would like to expose a parameter that allows this behavior to be changed so that we can set the PodName value to be consistent with other deployment types.

Something like:

prefer_controller_name_for_statefulset: true|false

With the default maintaining the current behavior.

Describe alternatives you've considered

We are exploring deploying each application into an isolated namespace to be able to get that aggregate alarm capability back.

Additional context

No response

[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.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.

[gthomson31]

This is still an issue - awaiting PR Review