# Option List host.name not all values

**URL:** <https://discuss.elastic.co/t/option-list-host-name-not-all-values/171762>\
**Category:** Kibana\
**Created:** [March 11, 2019, 12:37pm UTC](https://discuss.elastic.co/t/option-list-host-name-not-all-values/171762 "2019-03-11T12:37:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeckgit](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jeckgit/32/42336_2.png) [@jeckgit](https://discuss.elastic.co/u/jeckgit)\
**Post date:** [March 11, 2019, 12:37pm UTC](https://discuss.elastic.co/t/option-list-host-name-not-all-values/171762/1 "2019-03-11T12:37:29Z")

</div>

I don't get all the host names in the optionlist, which were sent via filebeat to elasticsearch.  
You will see what I mean in the Screenshots:

 ![optionlist](https://us1.discourse-cdn.com/elastic/original/3X/8/3/83d70b317bb0ee8a93035a0c985a952f34e327c9.jpeg)  
 ![table](https://us1.discourse-cdn.com/elastic/original/3X/a/a/aa6499db03ffb03334244f682a9f6c5207e4226f.jpeg)

In the second screen you can see, that there are obviously more than 3 hosts available.  
My question is, how do I fix that?

I know it refers to [https://github.com/elastic/kibana/issues/17388](https://github.com/elastic/kibana/issues/17388). But where and how can I change the `terminate_after` for the `host.name` preset?

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [March 11, 2019, 9:45pm UTC](https://discuss.elastic.co/t/option-list-host-name-not-all-values/171762/2 "2019-03-11T21:45:49Z")

</div>

I thought this might be a time range bug, but I tested locally and it is not. Seems like a document count issue, due to the way that list is populated. Since that issue is still open, those values are likely still hard-coded and nothing short of a custom Kibana build will let you change them.

---

<div class="post-metadata">

**Author:** ![jeckgit](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jeckgit/32/42336_2.png) [@jeckgit](https://discuss.elastic.co/u/jeckgit)\
**Post date:** [March 12, 2019, 8:11am UTC](https://discuss.elastic.co/t/option-list-host-name-not-all-values/171762/3 "2019-03-12T08:11:50Z")

</div>

So will this 'bug' be changed in the next version of Kibana? Would be good to know.

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [March 19, 2019, 7:37pm UTC](https://discuss.elastic.co/t/option-list-host-name-not-all-values/171762/4 "2019-03-19T19:37:03Z")

</div>

Looking at that issue, it seems like a number of users are running into that problem. I don't know if the team that maintains that is actively working on a fix or not, but [https://github.com/elastic/kibana/issues/17388](https://github.com/elastic/kibana/issues/17388) is where to watch to find out, ask questions, and otherwise discuss it.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 16, 2019, 7:37pm UTC](https://discuss.elastic.co/t/option-list-host-name-not-all-values/171762/5 "2019-04-16T19:37:07Z")

</div>

Closed on April 16, 2019, 7:37pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.