host.name assigned with pod.name

[crespocarlos]

Describe the bug

When viewing the Hosts UI with Python APM service active in a k8s pod, Python agent monitored services report the pod name in the host.name, which makes the Hosts View display hosts that do not correlate with hosts monitored by the system integration.

Steps to reproduce

• Run a python APM instrumented service in a k8s pod
• Ingest that into ES
• Open the Infra UI

edge-oblt can be used for the above.

Expected behavior

Only hosts (VMs) are expected to be present in the Hosts View.

Additional context

Sample doc

{
  "_index": ".ds-metrics-apm.app.opbeans_python-default-2024.07.17-000005",
  "_id": "w64vxZABi-i5Y9bCXbbY",
  "_score": 0,
  "_source": {
    "agent": {
      "activation_method": "unknown",
      "name": "python",
      "version": "6.22.3"
    },
    "cloud": {
      "availability_zone": "us-central1-c",
      "instance": {
        "id": "9037683114632400191",
        "name": "gke-edge-oblt-edge-oblt-pool-8fc2868f-gsl6"
      },
      "machine": {
        "type": "e2-highcpu-4"
      },
      "project": {
        "id": "elastic-observability"
      },
      "provider": "gcp",
      "region": "us-central1"
    },
    "data_stream": {
      "dataset": "apm.app.opbeans_python",
      "namespace": "default",
      "type": "metrics"
    },
    "host": {
      "architecture": "x86_64",
      "hostname": "opbeans-python-5967fc4646-p4d87",
      "ip": "34.132.199.117",
      "name": "opbeans-python-5967fc4646-p4d87",
      "os": {
        "platform": "linux"
      }
    },
    "metricset": {
      "name": "app"
    }
  }
}

[crespocarlos]

I had a quick call with @Mpdreamz , and he explained that the non-matching host names shipped by APM agents are due to missing configuration as exemplified in this comment https://github.com/elastic/observability-dev/issues/3321#issuecomment-2236909682.