Enhancing k8sattributesprocessor for Multi-Dimensional Metrics Collection

[tomatopunk]

Component(s)

processor/k8sattributes

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

Currently, the k8sattributesprocessor retrieves the pod identifier value from a single resource attribute. However, in many scenarios, this is not sufficient.

For example, while the collection target might be a node or machine, the metrics collected could be at the container level or related to specific Kubernetes resources, such as pods, containers, or even PVs and PVCs, as seen with tools like google/cAdvisor and kubelet.

Describe the solution you'd like

We need to add an attribute scope before inserting metadata, such as labels or container IDs.
By introducing this attribute scope, we can prioritize resource attribute scopes effectively.

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners:

• processor/k8sattributes: @dmitryax @fatsheep9146 @TylerHelmuth

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

[tomatopunk]

@dmitryax @fatsheep9146 @TylerHelmuth
What do you think? I'm really excited to complete this feature.

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

• processor/k8sattributes: @dmitryax @fatsheep9146 @TylerHelmuth @ChrsMark

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

[ChrsMark]

If understand this correctly, the proposal is to add support for associating metrics with other resources like Nodes? I think this request makes sense.

i.e.: kubeletstats receiver can provide Node's cpu metrics. We want these metrics to be populated with additional K8s metadata from the processor.