# Kibana Monitoring
**URL:** https://discuss.elastic.co/t/kibana-monitoring/142631
**Category:** Kibana
**Created:** [August 1, 2018, 5:20pm UTC](https://discuss.elastic.co/t/kibana-monitoring/142631 "2018-08-01T17:20:14Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@lcui\_dxc](https://discuss.elastic.co/u/lcui_dxc)
#### Post date: [August 1, 2018, 5:20pm UTC](https://discuss.elastic.co/t/kibana-monitoring/142631/1 "2018-08-01T17:20:14Z")
Hello there,
I'm new to ELK on AWS, I just set up an ELK cluster on one Node and set up filebeat and metricbeat on a separate linux server. On Kibana, I can see from Discovery, the data/logs coming from filebeat and metricbeat, but on Monitoring, I can only see the metrics on the ELK node.
I can see the metrics on Dashborad, though. Is this right? If not, what should I do to use Monitoring on Kibana to monitor the target server where the metricbeat runs on?
Thanks
---
### Author:  [@tsullivan](https://discuss.elastic.co/u/tsullivan)
#### Post date: [August 1, 2018, 8:34pm UTC](https://discuss.elastic.co/t/kibana-monitoring/142631/2 "2018-08-01T20:34:11Z")
It sounds like you are saying that your Monitoring dashboards are missing the info for your Beats. Or in other words, you are trying to set up Beats Monitoring, as in [https://www.elastic.co/guide/en/kibana/current/beats-page.html](https://www.elastic.co/guide/en/kibana/current/beats-page.html)
Take a look at the guide to configure Beats for Monitoring: [https://www.elastic.co/guide/en/beats/filebeat/current/monitoring.html](https://www.elastic.co/guide/en/beats/filebeat/current/monitoring.html). If Elasticsearch is the output for your Beats, adding `xpack.monitoring.enabled: true` to the YML might be all you need to do.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 29, 2018, 8:34pm UTC](https://discuss.elastic.co/t/kibana-monitoring/142631/3 "2018-08-29T20:34:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.