In any case, Kibana always prompts that it is using `APM Server binary` instead of `Elastic Agent`

[linghengqian]

• I came from https://discuss.elastic.co/t/in-any-case-kibana-always-prompts-that-it-is-using-apm-server-binary-instead-of-elastic-agent/366306?u=linghengqian , in order to avoid the original discussion being locked due to no reply for 28 days, I opened the current github issue.

• Even if I deploy Elastic Agent with APM integration enabled, Kibana still prompts that it is using APM Server binary instead of Elastic Agent. The following screenshots are from a Kibana 8.15.1 instance deployed from a Docker Image with a URL similar to http://localhost:5601/app/apm/settings/schema.

• 

• But I did register 2 Elastic Agents via the settings of http://localhost:5601/app/fleet/agents, one is Fleet Server and the other has the Elastic APM integration strategy turned on.

• 

• This uses ElasticSearch 8.15.1, Kibana 8.15.1, Elastic Agent 8.15.1, and the Docker Image from the Elastic Package Registry 8.15.1.

• I’m not sure if I should try to provide reproducible steps, since this seems easy to reproduce. The main reason is that this finding comes from a Chinese article https://www.yuque.com/linghengqian/meve2v/kezd0g2m3lfuz38q , and that Chinese article has 15148 words.

• I think it is unreasonable that http://localhost:5601/app/apm/settings/schema indicates that APM Server binary is being used, although this does not affect the further use of Elastic APM.

[arTG0D]

I had the same problem ES v8.13.3 Kibana v8.13.3 ES Agent v8.13.3

[elasticmachine]

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

[elasticmachine]

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)