For UI mapping of data, use pod name where container id is not present or has no information

[jackshirazi]

Describe the feature:
There is no standard for containerID extraction from within the container, so the extraction uses heuristics and these can lead to incorrect IDs. With GKE Autopilot it seems impossible to get the correct ID, see elastic/apm-agent-java#3510

Describe a specific use case for the feature:
Presented in elastic/apm-agent-java#3510 - if this feature is selected for work, followup for testing may be possible with the various stakeholders in that issue

[roshan-elastic]

Hey @akhileshpok, when you get a sec do you think your team could take a look to see if this is something that could be potentially resolved in agent itself (or maybe OTel would fix it)?

Trying to figure out if we need to build around this in the UI or not.

[elasticmachine]

Pinging @elastic/apm-ui (Team:APM)

[trainings]

Hi all.
Are there any news/updates on this issue?

[smith]

There's discussion in the otel community about this, @AlexanderWert @tommyers-elastic. There's an issue on the containerd repo that talks about this: containerd/containerd#8185

It's mentioned on an RFC about evolving host.id: open-telemetry/semantic-conventions#581

For UI mapping of data, use pod name where container id is not present or has no information

I'm not sure if this mapping should happen in the UI. We already make some opaque transformations of fields that can cause confusion. The user should be able to transparently know how data changed in their pipeline.