# Elk Stack 5.3 Issue with Metricbeat Dashboards on Kibana:::Visualize: Fielddata is disabled on text fields by default **URL:** \ **Category:** Beats\ **Tags:** metricbeat\ **Created:** [April 11, 2017, 6:23pm UTC](https://discuss.elastic.co/t/elk-stack-5-3-issue-with-metricbeat-dashboards-on-kibana-visualize-fielddata-is-disabled-on-text-fields-by-default/82035 "2017-04-11T18:23:26Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Ramakrishna\_K](https://avatars.discourse-cdn.com/v4/letter/r/3bc359/32.png) [@Ramakrishna\_K](https://discuss.elastic.co/u/Ramakrishna_K)\ **Post date:** [April 11, 2017, 6:23pm UTC](https://discuss.elastic.co/t/elk-stack-5-3-issue-with-metricbeat-dashboards-on-kibana-visualize-fielddata-is-disabled-on-text-fields-by-default/82035/1 "2017-04-11T18:23:26Z")
Hi, I have installed elk stack 5.3 with metricbeat. After this I have loaded the metric beat dashboards. When I open the Kibana with any sample dashboard I am getting below error. ![](https://us1.discourse-cdn.com/elastic/original/3X/2/3/23000129a3bbc38f9e77bc44744ea98b6399fe64.png) I have read several posts. But I am not able to understand how to fix this issue? Could any one please help? Regards, Ramakrishna ---
**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\ **Post date:** [April 12, 2017, 12:21am UTC](https://discuss.elastic.co/t/elk-stack-5-3-issue-with-metricbeat-dashboards-on-kibana-visualize-fielddata-is-disabled-on-text-fields-by-default/82035/2 "2017-04-12T00:21:15Z")
Hi The error message you are seeing is stating that for text fields there are two way to aggregate or sort the data, either enable field data at the cost of using memory or use/add a keyword field. Field data can consume a lot of heap space, especially when loading high cardinality text fields, hence its disabled by default. Ref : [https://www.elastic.co/guide/en/elasticsearch/reference/current/fielddata.html#\_fielddata\_is\_disabled\_on\_literal\_text\_literal\_fields\_by\_default](https://www.elastic.co/guide/en/elasticsearch/reference/current/fielddata.html#_fielddata_is_disabled_on_literal_text_literal_fields_by_default) Once you do that it will resolve the error message. More details can be found here : [https://github.com/elastic/elasticsearch/issues/22768](https://github.com/elastic/elasticsearch/issues/22768) Thanks Rashmi ---
**Author:** ![Ramakrishna\_K](https://avatars.discourse-cdn.com/v4/letter/r/3bc359/32.png) [@Ramakrishna\_K](https://discuss.elastic.co/u/Ramakrishna_K)\ **Post date:** [April 12, 2017, 5:38am UTC](https://discuss.elastic.co/t/elk-stack-5-3-issue-with-metricbeat-dashboards-on-kibana-visualize-fielddata-is-disabled-on-text-fields-by-default/82035/3 "2017-04-12T05:38:38Z")
Hi Rashmi, Thanks for the reply. I have seen the posts. But still the information is not clear. I have the below index on elastic search: ``` [root@elk-stack ~]# curl -XGET 'localhost:9200/_cat/indices?v&pretty' health status index uuid pri rep docs.count docs.deleted store.size pri.store.size yellow open my_index FOKpTYq5QdCeJzShlLxzkg 5 1 0 0 795b 795b yellow open index bk3v-YO6SD-0-qAAMboa7g 5 1 0 0 795b 795b yellow open metricbeat-2017.04.11 lrdPCokkSgGzgAYccUI5AQ 5 1 740131 0 260.7mb 260.7mb yellow open metricbeat-2017.04.12 Ov_9hU8fQki4kcsmxA66XQ 5 1 586433 0 207.3mb 207.3mb yellow open .kibana O4FjI-DrQY-APDIQOlmlgw 1 1 96 68 284.7kb 284.7kb ``` The field data enabling is required for me, because I am using Metric beats. When I use metric beats lot of information has text related data like process names, Network interface names, Host names etc.. So could you please give an example on how to enable fielddata for metricbeats? Thanks in advance. Regards, Ramakrishna ---
**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\ **Post date:** [April 12, 2017, 5:48am UTC](https://discuss.elastic.co/t/elk-stack-5-3-issue-with-metricbeat-dashboards-on-kibana-visualize-fielddata-is-disabled-on-text-fields-by-default/82035/4 "2017-04-12T05:48:35Z")
> [@Ramakrishna\_K](#): > > So could you please give an example on how to enable fielddata for metricbeats? Hi RamaKrishna, Can you run GET /metricbeat-\* in Dev tools and share the output? Also do enable fielddata:true in metricbeat.template.json . For Ex: ```auto "id": { "type": "text", "fielddata":"true" }, "image": { "type": "text", "fielddata": true }, "name": { "type": "text", "fielddata":true }, ``` Note that this can however use significant memory. My guess is the setting in the template file is not being propagated to ES. If you don't have any data you need to preserve, you can try deleting the index and starting again. You can also try sending data to a new index name. Hope this helps.. Thanks Rashmi ---
**Author:** ![Ramakrishna\_K](https://avatars.discourse-cdn.com/v4/letter/r/3bc359/32.png) [@Ramakrishna\_K](https://discuss.elastic.co/u/Ramakrishna_K)\ **Post date:** [April 12, 2017, 6:13am UTC](https://discuss.elastic.co/t/elk-stack-5-3-issue-with-metricbeat-dashboards-on-kibana-visualize-fielddata-is-disabled-on-text-fields-by-default/82035/5 "2017-04-12T06:13:29Z")
Hi Rashmi, Many thanks for the quick reply. But The out I am not able to paste in the message or attach. How can I share the output? Also I have only one text field in the metricbeat.template.json. ``` "meta": { "norms": false, "type": "text", "fielddata":true ``` I added fielddata:true here. is this ok? Regards, Ramakrishna ---
**Author:** ![Ramakrishna\_K](https://avatars.discourse-cdn.com/v4/letter/r/3bc359/32.png) [@Ramakrishna\_K](https://discuss.elastic.co/u/Ramakrishna_K)\ **Post date:** [April 12, 2017, 6:46am UTC](https://discuss.elastic.co/t/elk-stack-5-3-issue-with-metricbeat-dashboards-on-kibana-visualize-fielddata-is-disabled-on-text-fields-by-default/82035/6 "2017-04-12T06:46:56Z")
Hi Rashmi, I have uploaded the GET /metricbeat-\* output in the below location. > **[metricbeat.json](https://www.dropbox.com/s/s6ljjrgbktsfp71/metricbeat.json?dl=0)** > > Shared with Dropbox Regards, Ramakrishna ---
**Author:** ![Ramakrishna\_K](https://avatars.discourse-cdn.com/v4/letter/r/3bc359/32.png) [@Ramakrishna\_K](https://discuss.elastic.co/u/Ramakrishna_K)\ **Post date:** [May 3, 2017, 8:12am UTC](https://discuss.elastic.co/t/elk-stack-5-3-issue-with-metricbeat-dashboards-on-kibana-visualize-fielddata-is-disabled-on-text-fields-by-default/82035/7 "2017-05-03T08:12:35Z")
Can anyone help me on this? I see many posts related to this. But no solution. Thanks in advance. Regards, Ramakrishna ---
**Author:** ![tudor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tudor/32/3753_2.png) [@tudor](https://discuss.elastic.co/u/tudor)\ **Post date:** [May 9, 2017, 12:06pm UTC](https://discuss.elastic.co/t/elk-stack-5-3-issue-with-metricbeat-dashboards-on-kibana-visualize-fielddata-is-disabled-on-text-fields-by-default/82035/8 "2017-05-09T12:06:33Z")
@Ramakrishna_K If you can, I'd recommend dropping the existing metricbeat indices (`DELETE /metricbeat-*`) in Console, then make sure you do the following: - The mapping template that we provide with the Beats should be loaded. Metricbeat does that automatically, so there's usually nothing to do, but you can make sure it worked by: stop metricbeat, run `DELETE /_template/metricbeat`, start metricbeat again, check that `GET /_template/metricbeat` returns a long document. - The Metricbeat dashboards are loaded correctly. Run `./scripts/import_dashboards` and then make sure to **not** refresh the index pattern in Kibana, as that can break the dashboards again. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 6, 2017, 12:14pm UTC](https://discuss.elastic.co/t/elk-stack-5-3-issue-with-metricbeat-dashboards-on-kibana-visualize-fielddata-is-disabled-on-text-fields-by-default/82035/9 "2017-06-06T12:14:56Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.