# Fields in Kibana 5 are non-searchable and non-aggregatable

**URL:** <https://discuss.elastic.co/t/fields-in-kibana-5-are-non-searchable-and-non-aggregatable/70565>\
**Category:** Kibana\
**Created:** [January 4, 2017, 2:30pm UTC](https://discuss.elastic.co/t/fields-in-kibana-5-are-non-searchable-and-non-aggregatable/70565 "2017-01-04T14:30:25Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![BigFunger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bigfunger/32/7323_2.png) [@BigFunger](https://discuss.elastic.co/u/BigFunger)\
**Post date:** [January 4, 2017, 4:52pm UTC](https://discuss.elastic.co/t/fields-in-kibana-5-are-non-searchable-and-non-aggregatable/70565/2 "2017-01-04T16:52:23Z")

</div>

> [@aviral\_srivastava](#):
>
> I have configured topbeat 1.2 topbeat.yml to point to linux server

Do you mean that Elasticsearch is running on your linux server, and that you are pointing the topbeat instance on your windows machine to it?

> [@aviral\_srivastava](#):
>
> I have not started Topbeat on linux

Are you using Logstash to index the data from topbeat, or did you configure it to dump directly into Elasticsearch?

If you are dumping directly into elasticsearch, I don't think that you need to manually load the index template.

---

_[View the full topic](https://discuss.elastic.co/t/fields-in-kibana-5-are-non-searchable-and-non-aggregatable/70565)._