# Monitoring Kibana, Elasticsearch via APM

**URL:** <https://discuss.elastic.co/t/monitoring-kibana-elasticsearch-via-apm/359550>\
**Category:** APM\
**Tags:** agent-explorer\
**Created:** [May 15, 2024, 1:18pm UTC](https://discuss.elastic.co/t/monitoring-kibana-elasticsearch-via-apm/359550 "2024-05-15T13:18:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![adis3421](https://avatars.discourse-cdn.com/v4/letter/a/46a35a/32.png) [@adis3421](https://discuss.elastic.co/u/adis3421)\
**Post date:** [May 15, 2024, 1:18pm UTC](https://discuss.elastic.co/t/monitoring-kibana-elasticsearch-via-apm/359550/1 "2024-05-15T13:18:27Z")

</div>

Hi,

I installed APM with Fleet integration and chail, used it to monitor elastica and kibane, I followed this article [How to activate APM in Kibana and Elasticsearch to gain next-level alerting insights | Elastic Blog](https://www.elastic.co/blog/apm-kibana-elasticsearch-alerting-insights) unfortunately I only get the kibana service, I don't have kibana-frontend and elasticsearch. Maybe someone knows how to do it properly in version 8.13?

---

<div class="post-metadata">

**Author:** ![erikg](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@erikg](https://discuss.elastic.co/u/erikg)\
**Post date:** [May 16, 2024, 5:17pm UTC](https://discuss.elastic.co/t/monitoring-kibana-elasticsearch-via-apm/359550/2 "2024-05-16T17:17:21Z")

</div>

Hello,

I also had the same issue.  
I believe you still need to toggle on RUM settings  
I am also on 8.13.4

---

<div class="post-metadata">

**Author:** ![adis3421](https://avatars.discourse-cdn.com/v4/letter/a/46a35a/32.png) [@adis3421](https://discuss.elastic.co/u/adis3421)\
**Post date:** [May 24, 2024, 2:12pm UTC](https://discuss.elastic.co/t/monitoring-kibana-elasticsearch-via-apm/359550/3 "2024-05-24T14:12:59Z")

</div>

> [@erikg](#):
>
> I also had the same issue.  
> I believe you still need to toggle on RUM settings  
> I am also on 8.13.4

HI,

There is something wrong with my cluster which is on Oracle Linux, because on Debian in another company everything works fine, the settings are the same, the operating system is different.
