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

**URL:** https://discuss.elastic.co/t/in-any-case-kibana-always-prompts-that-it-is-using-apm-server-binary-instead-of-elastic-agent/366306
**Category:** Kibana
**Tags:** docker
**Created:** [September 10, 2024, 10:16am UTC](https://discuss.elastic.co/t/in-any-case-kibana-always-prompts-that-it-is-using-apm-server-binary-instead-of-elastic-agent/366306 "2024-09-10T10:16:57Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![linghengqian](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/linghengqian/32/103651_2.png) [@linghengqian](https://discuss.elastic.co/u/linghengqian)
#### Post date: [September 10, 2024, 10:16am UTC](https://discuss.elastic.co/t/in-any-case-kibana-always-prompts-that-it-is-using-apm-server-binary-instead-of-elastic-agent/366306/1 "2024-09-10T10:16:57Z")

</div>

- 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`.
- ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/7/172a651159b065a78d5135233a05b722d6b87805.png)
- 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.
- ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/4/e45e9c569318f12572a303844cb02ae9e2f5b8a6.png)
- 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](https://www.yuque.com/linghengqian/meve2v/kezd0g2m3lfuz38q) , and that Chinese article has `14,479` 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.

---

<div class="post-metadata">

### Author: ![linghengqian](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/linghengqian/32/103651_2.png) [@linghengqian](https://discuss.elastic.co/u/linghengqian)
#### Post date: [October 7, 2024, 12:32pm UTC](https://discuss.elastic.co/t/in-any-case-kibana-always-prompts-that-it-is-using-apm-server-binary-instead-of-elastic-agent/366306/2 "2024-10-07T12:32:54Z")

</div>

I've opened [In any case, Kibana always prompts that it is using `APM Server binary` instead of `Elastic Agent` · Issue #194356 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/194356) to avoid the current discussion being closed after 28 days of no response.
