Skip to content

Verify ECS alignment in container fields reported by kubernetes module and meta processor #23585

@ChrsMark

Description

@ChrsMark

We need to make sure that we have consistent way of aligning common ECS fields across integrations reporting same resource information. An example can be container.image.name and kubernetes.container.image (added at #20984) which is actually the same field but it not aliased like what is happening with Docker:

docker.container.image
type: alias
alias to: container.image.name

Update:
Verify that state_* metricsets follow ECS. For instance testing state_container datastream of k8s package I get:

kubernetes/state_container default:
[0] field "container.runtime" is undefined
[1] field "kubernetes.container.image" is undefined
[2] field "kubernetes.container.name" is undefined
[3] field "kubernetes.namespace" is undefined
[4] field "kubernetes.node.name" is undefined
[5] field "kubernetes.pod.name" is undefined

So kubernetes.container.* seem to need to be changed.

Metadata

Metadata

Assignees

Labels

Team:IntegrationsLabel for the Integrations teamcontainersRelated to containers use caseecskubernetesEnable builds in the CI for kubernetes

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions