# Kibana dashboard cannot load metricbeat data
**URL:** https://discuss.elastic.co/t/kibana-dashboard-cannot-load-metricbeat-data/300933
**Category:** Kibana
**Created:** [March 29, 2022, 8:57am UTC](https://discuss.elastic.co/t/kibana-dashboard-cannot-load-metricbeat-data/300933 "2022-03-29T08:57:57Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@leelax22](https://discuss.elastic.co/u/leelax22)
#### Post date: [March 29, 2022, 8:57am UTC](https://discuss.elastic.co/t/kibana-dashboard-cannot-load-metricbeat-data/300933/1 "2022-03-29T08:57:57Z")
I am testing to monitor aks using ELK stack and beat.
The installation is completed with version 8.1.0, and it is confirmed that data is well accumulated in Kibana through the metricbeat-\* index.
Because I did not connect directly from metricbeat to Elasticsearch and went through logstash, it was necessary to install a dashboard separately, and it was also completed by connecting to the metricbeat pod separately.
```auto
./metricbeat setup -e \
-E output.logstash.enabled=false \
-E output.elasticsearch.enabled=true \
-E output.elasticsearch.hosts=['https://elasticsearch-master:9200'] \
-E output.elasticsearch.ssl.verification_mode=none \
-E output.elasticsearch.username=elastic \
-E output.elasticsearch.password= ******* \
-E setup.kibana.ssl.enabled=true \
-E setup.kibana.host="https://kibana-kibana:5601" \
-E setup.kibana.ssl.verification_mode=none \
-E setup.ilm.overwrite=true
```
First, I have a total of 3 nodes, but there is a problem in the log that [kubernetes.node.name] is split.
Second, despite the fact that there are logs that are clearly collected as [kubernetes.node.name],
Nodes [Metricbeat Kubernetes] ECS in visualize library fails to load those items. Same problem with pods and deployments.
Where should I look? If anyone knows, please help.
---
### Author:  [@leelax22](https://discuss.elastic.co/u/leelax22)
#### Post date: [March 30, 2022, 1:45am UTC](https://discuss.elastic.co/t/kibana-dashboard-cannot-load-metricbeat-data/300933/2 "2022-03-30T01:45:27Z")
first problem solved.
I use [kubernetes.node.name.keyword] instead [kubernetes.node.name]
it works.
---
### Author:  [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [March 30, 2022, 3:08am UTC](https://discuss.elastic.co/t/kibana-dashboard-cannot-load-metricbeat-data/300933/3 "2022-03-30T03:08:16Z")
The reason you are having these problems is that you need to run complete `metricbeat setup` not just load the dashboards
`metricbeat setup` also loads. The templates for the mappings are correct. The fact that you're having to use keywords means the mapping is not correct.
Take a look at this post [here](https://discuss.elastic.co/t/metricbeat-to-logstash-to-elasticsearch-cannot-see-any-hosts-defined-but-data-is-definitely-coming-in/275715/2)
---
### Author:  [@leelax22](https://discuss.elastic.co/u/leelax22)
#### Post date: [March 31, 2022, 1:28am UTC](https://discuss.elastic.co/t/kibana-dashboard-cannot-load-metricbeat-data/300933/4 "2022-03-31T01:28:44Z")
Thank you very much for your reply. The process seems a bit cumbersome. I will try it and leave a review. 😃
---
### Author:  [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [March 31, 2022, 5:48am UTC](https://discuss.elastic.co/t/kibana-dashboard-cannot-load-metricbeat-data/300933/5 "2022-03-31T05:48:03Z")
It's not my process. It's how it works.
If you want to use metricbeat correctly, you need to run setup, and set up all the assets, not just dashboards.
After you do that, if you want to pump it through logstash, that's fine
In short, I always say run metricbeat directly to Elasticsearch and Once that all works then send metricbeat data through logstash.
At this point, logstash is just a collecting forward mechanism.
Pretty straight forward.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 28, 2022, 5:48am UTC](https://discuss.elastic.co/t/kibana-dashboard-cannot-load-metricbeat-data/300933/6 "2022-04-28T05:48:47Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.