# ELK 7 The request for this panel failed
**URL:** https://discuss.elastic.co/t/elk-7-the-request-for-this-panel-failed/177136
**Category:** Beats
**Tags:** metricbeat
**Created:** [April 16, 2019, 6:12pm UTC](https://discuss.elastic.co/t/elk-7-the-request-for-this-panel-failed/177136 "2019-04-16T18:12:53Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@teamg](https://discuss.elastic.co/u/teamg)
#### Post date: [April 16, 2019, 6:12pm UTC](https://discuss.elastic.co/t/elk-7-the-request-for-this-panel-failed/177136/1 "2019-04-16T18:12:53Z")
I have an ELK 6.7 and an ELK 7 both on single nodes. They're configured the same with metricbeat installed to monitor the nodes. When I look at the Host Overview Dashboard on ELK 7 I see:
This does not occur on the ELK 6.7 node. Are there any changes between version which would cause this?
---
### Author:  [@Chernomazov](https://discuss.elastic.co/u/Chernomazov)
#### Post date: [April 17, 2019, 5:18pm UTC](https://discuss.elastic.co/t/elk-7-the-request-for-this-panel-failed/177136/2 "2019-04-17T17:18:01Z")
[https://www.elastic.co/guide/en/elasticsearch/reference/current/fielddata.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/fielddata.html)
Elasticsearch 7.0 uses keyword field for aggregation of fields with text type.
You need to upgrade Metricbeat to 7.0 version: [https://www.elastic.co/guide/en/beats/libbeat/7.0/upgrading-6-to-7.html](https://www.elastic.co/guide/en/beats/libbeat/7.0/upgrading-6-to-7.html)
---
### Author:  [@teamg](https://discuss.elastic.co/u/teamg)
#### Post date: [April 17, 2019, 7:02pm UTC](https://discuss.elastic.co/t/elk-7-the-request-for-this-panel-failed/177136/3 "2019-04-17T19:02:18Z")
Metricbeat is at version 7:
> [root@elk ~]# rpm -qa|grep metric
> metricbeat-7.0.0-1.x86\_64
---
### Author:  [@Chernomazov](https://discuss.elastic.co/u/Chernomazov)
#### Post date: [April 18, 2019, 5:22am UTC](https://discuss.elastic.co/t/elk-7-the-request-for-this-panel-failed/177136/4 "2019-04-18T05:22:45Z")
Is Elasticsearch index template for Metricbeat [upgraded](https://www.elastic.co/guide/en/beats/libbeat/7.0/upgrading-6-to-7.html#upgrade-index-template)?
Are Kibana dashboards for Metrcibeat [upgraded](https://www.elastic.co/guide/en/beats/libbeat/7.0/upgrading-6-to-7.html#_upgrade_dashboards)?
---
### Author:  [@teamg](https://discuss.elastic.co/u/teamg)
#### Post date: [April 22, 2019, 5:05pm UTC](https://discuss.elastic.co/t/elk-7-the-request-for-this-panel-failed/177136/5 "2019-04-22T17:05:21Z")
This is a fresh install of ELK 7 across the board, Elastic, Logstash, Kibana, Metricbeat.
---
### Author:  [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [April 23, 2019, 11:10am UTC](https://discuss.elastic.co/t/elk-7-the-request-for-this-panel-failed/177136/6 "2019-04-23T11:10:25Z")
Do you send the data through LS? Did you load the index template? What is the versioning scheme you use for the indices?
---
### Author:  [@teamg](https://discuss.elastic.co/u/teamg)
#### Post date: [April 23, 2019, 2:24pm UTC](https://discuss.elastic.co/t/elk-7-the-request-for-this-panel-failed/177136/7 "2019-04-23T14:24:32Z")
Yes, my data is going through ES. Below is my metricbeat.yml:
> [root@elk metricbeat]# cat metricbeat.yml |grep -v #|grep -v -e '^$'
```auto
> metricbeat.config.modules:
> path: ${path.config}/conf.d/*.yml
> reload.period: 10s
> reload.enabled: false
> metricbeat.max_start_delay: 10s
> metricbeat.modules:
> - module: system
> metricsets:
> enabled: true
> period: 10s
> processes: ['.*']
> output.elasticsearch:
> enabled: true
> hosts: ["localhost:9200"]
> setup.dashboards.enabled: true
> setup.dashboards.directory: ${path.home}/kibana
> setup.template.enabled: true
> setup.template.name: "metricbeat-%{[beat.version]}"
> setup.template.pattern: "metricbeat-%{[beat.version]}-*"
> setup.template.fields: "${path.config}/fields.yml"
> setup.template.settings:
> setup.kibana:
> logging.to_files: true
> logging.files:
```
---
### Author:  [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [April 26, 2019, 9:05am UTC](https://discuss.elastic.co/t/elk-7-the-request-for-this-panel-failed/177136/8 "2019-04-26T09:05:13Z")
What is the reason you have setup template in there? In general I would not recommend to modify the defaults (it looks like the defaults?) if not needed. With 7.0 Beats start to use ILM by default.
---
### Author:  [@teamg](https://discuss.elastic.co/u/teamg)
#### Post date: [April 26, 2019, 2:36pm UTC](https://discuss.elastic.co/t/elk-7-the-request-for-this-panel-failed/177136/9 "2019-04-26T14:36:59Z")
I changed setup.template.enabled to false and restarted metricbeat. I deleted the metricbeat index to get a fresh start but I still see the same errors. Not sure what I'm missing here.
> metricbeat.config.modules:
> path: ${path.config}/conf.d/\*.yml
> reload.period: 10s
> reload.enabled: false
> metricbeat.max\_start\_delay: 10s
> metricbeat.modules:
>
> - module: system
> metricsets:
> enabled: true
> period: 10s
> processes: ['._']
> output.elasticsearch:
> enabled: true
> hosts: ["localhost:9200"]
> **setup.template.enabled: false**
> setup.template.name: "metricbeat-%{[beat.version]}"
> setup.template.pattern: "metricbeat-%{[beat.version]}-_"
> setup.template.fields: "${path.config}/fields.yml"
> setup.template.settings:
> setup.kibana:
> logging.to\_files: true
> logging.files:
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 24, 2019, 2:37pm UTC](https://discuss.elastic.co/t/elk-7-the-request-for-this-panel-failed/177136/10 "2019-05-24T14:37:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.