# Monitoring displays http\_address instead of host **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-monitoring\ **Created:** [December 17, 2018, 9:38am UTC](https://discuss.elastic.co/t/monitoring-displays-http-address-instead-of-host/161106 "2018-12-17T09:38:00Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Dan\_Markhasin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dan_markhasin/32/14187_2.png) [@Dan\_Markhasin](https://discuss.elastic.co/u/Dan_Markhasin)\ **Post date:** [December 17, 2018, 9:38am UTC](https://discuss.elastic.co/t/monitoring-displays-http-address-instead-of-host/161106/1 "2018-12-17T09:38:01Z")
In the Monitoring tab for Logstash nodes, Kibana displays the node name and http\_address - which in our case is always "127.0.0.1:9600" as we don't bind the logstashes to external interfaces. As a result all of the logstash nodes appear like this and we have no way of knowing where they are actually running. Is this by design? Is it possible to somehow get it to display the host (from logstash\_stats.logstash.host) instead? ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [December 22, 2018, 2:17pm UTC](https://discuss.elastic.co/t/monitoring-displays-http-address-instead-of-host/161106/2 "2018-12-22T14:17:37Z")
Can you post a screenshot of your node listing? I suspect the problem you are trying to solve is somehow differentiate between the nodes in your listing? Also, are you setting `node.name` explicitly in your `logstash.yml` files? ---
**Author:** ![Dan\_Markhasin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dan_markhasin/32/14187_2.png) [@Dan\_Markhasin](https://discuss.elastic.co/u/Dan_Markhasin)\ **Post date:** [December 23, 2018, 6:46am UTC](https://discuss.elastic.co/t/monitoring-displays-http-address-instead-of-host/161106/3 "2018-12-23T06:46:31Z")
Yes, I think the screenshot makes it clear what the issue is: ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/f/7fbd490dfacc1ca7ea2a73bb1e024fa0c4f33ffe.png) It doesn't make a lot of sense to display the bind address (which I believe in most cases, for most users, would be localhost) instead of the actual http host. And yes we do set node.name explicitly (as you can see in the screenshot). ---
**Author:** ![Izek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/izek/32/37113_2.png) [@Izek](https://discuss.elastic.co/u/Izek)\ **Post date:** [December 23, 2018, 7:33am UTC](https://discuss.elastic.co/t/monitoring-displays-http-address-instead-of-host/161106/4 "2018-12-23T07:33:31Z")
If you change the http.host and http.port on the "Metrics Settings" section in the logstash.yml file. It will changed. the reason why it show that is because the default value of metrics settings. ---
**Author:** ![Dan\_Markhasin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dan_markhasin/32/14187_2.png) [@Dan\_Markhasin](https://discuss.elastic.co/u/Dan_Markhasin)\ **Post date:** [December 23, 2018, 7:51am UTC](https://discuss.elastic.co/t/monitoring-displays-http-address-instead-of-host/161106/5 "2018-12-23T07:51:30Z")
Based on the documentation, http.host and http.port tell logstash to which interface/port to bind to. Of course if I change it to bind to anything other than localhost it will work, but why would I want logstash to bind to any external interface and be accessible from outside the host? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 20, 2019, 7:51am UTC](https://discuss.elastic.co/t/monitoring-displays-http-address-instead-of-host/161106/6 "2019-01-20T07:51:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.