# Logstash Instance Missing from Kibana Monitoring

**URL:** <https://discuss.elastic.co/t/logstash-instance-missing-from-kibana-monitoring/186734>\
**Category:** Logstash\
**Created:** [June 20, 2019, 5:06pm UTC](https://discuss.elastic.co/t/logstash-instance-missing-from-kibana-monitoring/186734 "2019-06-20T17:06:44Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![jakecramer17](https://avatars.discourse-cdn.com/v4/letter/j/9dc877/32.png) [@jakecramer17](https://discuss.elastic.co/u/jakecramer17)\
**Post date:** [June 24, 2019, 8:35pm UTC](https://discuss.elastic.co/t/logstash-instance-missing-from-kibana-monitoring/186734/17 "2019-06-24T20:35:06Z")

</div>

I got it!

Thanks to [this thread](https://discuss.elastic.co/t/monitoring-logstash/162120), I found out that the commented path for `xpack.monitoring.elasticsearch.hosts` began with "`https://`", when it was supposed to be "`http://`" (remove the 's'). This was why Logstash was unable to retrieve my license information and failed to fetch my X-pack information from elasticsearch.

My problem was fixed by first correcting the `path.settings` field so Logstash would not ignore my configurations, then correcting the `xpack.monitoring.elasticsearch.hosts` field. Now Logstash is being monitored like I had hoped!

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/8/b8e4de53ab788dc697c0c31832f55698bd74b039.png)  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/5/656af66b96207c18929973f66cdc47848bed2d34.png)

---

_[View the full topic](https://discuss.elastic.co/t/logstash-instance-missing-from-kibana-monitoring/186734)._
