# Unable to View Imported Dashboards/Visualizations for Metricbeat

**URL:** https://discuss.elastic.co/t/unable-to-view-imported-dashboards-visualizations-for-metricbeat/69360
**Category:** Beats
**Tags:** metricbeat
**Created:** [December 18, 2016, 4:00pm UTC](https://discuss.elastic.co/t/unable-to-view-imported-dashboards-visualizations-for-metricbeat/69360 "2016-12-18T16:00:35Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![gupta.yuvraj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gupta.yuvraj/32/7550_2.png) [@gupta.yuvraj](https://discuss.elastic.co/u/gupta.yuvraj)
#### Post date: [December 18, 2016, 4:00pm UTC](https://discuss.elastic.co/t/unable-to-view-imported-dashboards-visualizations-for-metricbeat/69360/1 "2016-12-18T16:00:35Z")

</div>

I am using MetricBeat to capture statistics and send data to Logstash. Logstash then reads input from Beats and sends the data to Elasticsearch. Data is present in Elasticsearch & Kibana index shows the data read from Elasticsearch.

After Downloading and Loading Sample Beats dashboard, the dashboard/Visualizations give an error on opening. The error obtained is:-

**Saved "field" parameter is now invalid. Please select a new field.**  
**Visualize: "field" is a required parameter**

I have been able to debug the issue & found that the fields containing beat information such as [beat.name](http://beat.name), beat.hostname are being used by the sample beats dashboard which is non-aggregatable fields. However, when editing the visualization and changing the visualization value from [beat.name](http://beat.name) to beat.name.keyword works and the visualization is shown.

This issue is being observed for all the fields having datatype as string. Such fields without .keyword parameter are non-aggregatable while the fields with .keyword are aggregatable.

Is there any way to solve this issue so that fields without .keyword become aggregatable fields and Dashboard/Visualizations will be shown.

---

<div class="post-metadata">

### Author: ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [December 20, 2016, 8:34am UTC](https://discuss.elastic.co/t/unable-to-view-imported-dashboards-visualizations-for-metricbeat/69360/2 "2016-12-20T08:34:15Z")

</div>

Each beat comes shipped with an index template for elasticsearch. If you use Logstash in the middle, you need to load the template manually: [https://www.elastic.co/guide/en/beats/metricbeat/5.1/metricbeat-template.html](https://www.elastic.co/guide/en/beats/metricbeat/5.1/metricbeat-template.html)

This should solve your issue. The problem now is that the template will only apply to new indices.

---

<div class="post-metadata">

### Author: ![gupta.yuvraj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gupta.yuvraj/32/7550_2.png) [@gupta.yuvraj](https://discuss.elastic.co/u/gupta.yuvraj)
#### Post date: [December 20, 2016, 8:51am UTC](https://discuss.elastic.co/t/unable-to-view-imported-dashboards-visualizations-for-metricbeat/69360/3 "2016-12-20T08:51:52Z")

</div>

If I am sending data from Metricbeat to Logstash & then to Elasticsearch.  
While defining in Logstash config file, in Elastcisearch Output if I specify  
[Template.name](http://Template.name) & template.path property it will fetch the correct mappings to data in ES.

Is my understanding correct?

---

<div class="post-metadata">

### Author: ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [December 21, 2016, 8:40am UTC](https://discuss.elastic.co/t/unable-to-view-imported-dashboards-visualizations-for-metricbeat/69360/4 "2016-12-21T08:40:45Z")

</div>

So you reference the metricbeat template in logstash, correct?

---

<div class="post-metadata">

### Author: ![gupta.yuvraj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gupta.yuvraj/32/7550_2.png) [@gupta.yuvraj](https://discuss.elastic.co/u/gupta.yuvraj)
#### Post date: [December 21, 2016, 9:04am UTC](https://discuss.elastic.co/t/unable-to-view-imported-dashboards-visualizations-for-metricbeat/69360/5 "2016-12-21T09:04:39Z")

</div>

> [@ruflin](#):
>
> So you reference the metricbeat template in logstash, correct?

Yes will reference the metricbeat template in ES Output Plugin defined in Logstash Configuration file.

---

<div class="post-metadata">

### Author: ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [January 3, 2017, 7:44am UTC](https://discuss.elastic.co/t/unable-to-view-imported-dashboards-visualizations-for-metricbeat/69360/6 "2017-01-03T07:44:27Z")

</div>

I never tried it myself but that should work. Can you share your Logstash config?

---

<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: [January 31, 2017, 7:44am UTC](https://discuss.elastic.co/t/unable-to-view-imported-dashboards-visualizations-for-metricbeat/69360/7 "2017-01-31T07:44:39Z")

</div>

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