# Metricbeat dosen\`t shows in kibana\\Infrastructure after deleting index metricbeat-7.3.1
**URL:** https://discuss.elastic.co/t/metricbeat-dosen-t-shows-in-kibana-infrastructure-after-deleting-index-metricbeat-7-3-1/221056
**Category:** Beats
**Tags:** metricbeat
**Created:** [February 26, 2020, 2:30pm UTC](https://discuss.elastic.co/t/metricbeat-dosen-t-shows-in-kibana-infrastructure-after-deleting-index-metricbeat-7-3-1/221056 "2020-02-26T14:30:11Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@kvaga](https://discuss.elastic.co/u/kvaga)
#### Post date: [February 26, 2020, 2:30pm UTC](https://discuss.elastic.co/t/metricbeat-dosen-t-shows-in-kibana-infrastructure-after-deleting-index-metricbeat-7-3-1/221056/1 "2020-02-26T14:30:11Z")
ELK version 7.3.1
some time ago I`m setup ELK version 7.3 (on one server) and metricbeats (metricbeat version 7.3.1 ) on a few othres servers, all work fine, and kibana\Infrastructure shows CPU\Memory and other metrics
then i`m trynig to configure Index Lifecycle Policies... and index "metricbeat-7.3.1" was deleted.
metricbeats on servers create a new index in elasticsearch, BUT in kibana\Infrastructure dashboard is absent
screenshot [https://cloud.mail.ru/public/w8wW/4vhNSJvwR](https://cloud.mail.ru/public/w8wW/4vhNSJvwR)
---
### Author:  [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)
#### Post date: [February 26, 2020, 4:02pm UTC](https://discuss.elastic.co/t/metricbeat-dosen-t-shows-in-kibana-infrastructure-after-deleting-index-metricbeat-7-3-1/221056/2 "2020-02-26T16:02:25Z")
Hi!
Could you give more information about your setup? Did you run `metricbeat setup` again to setup indexes, templates, mappings etc after the deletion?
C.
---
### Author:  [@kvaga](https://discuss.elastic.co/u/kvaga)
#### Post date: [February 26, 2020, 4:57pm UTC](https://discuss.elastic.co/t/metricbeat-dosen-t-shows-in-kibana-infrastructure-after-deleting-index-metricbeat-7-3-1/221056/3 "2020-02-26T16:57:11Z")
fogot about this step
run now on one server
#metricbeat setup
Index setup finished.
Loading dashboards (Kibana must be running and reachable)
Loaded dashboards
but no effect
my metricbeat.yml
metricbeat.config.modules:
# Glob pattern for configuration loading
path: ${path.config}/modules.d/\*.yml
```
# Set to true to enable config reloading
reload.enabled: false
setup.template.settings:
index.number_of_shards: 1
index.codec: best_compression
setup.kibana:
host: "10.130.10.40:5601"
output.elasticsearch:
# Array of hosts to connect to.
hosts: ["10.130.10.40:9200"]
processors:
- add_host_metadata: ~
- add_cloud_metadata: ~
```
---
### Author:  [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)
#### Post date: [February 27, 2020, 8:41am UTC](https://discuss.elastic.co/t/metricbeat-dosen-t-shows-in-kibana-infrastructure-after-deleting-index-metricbeat-7-3-1/221056/4 "2020-02-27T08:41:00Z")
It the index you create the same `metricbeat-7.3.1`? Also the index patterns are the same? A lot of visualisations in Kibana are coupled with index-patterns so if you now have different ones, it might be a problem for Infra Ui too.
---
### Author:  [@kvaga](https://discuss.elastic.co/u/kvaga)
#### Post date: [February 27, 2020, 10:35am UTC](https://discuss.elastic.co/t/metricbeat-dosen-t-shows-in-kibana-infrastructure-after-deleting-index-metricbeat-7-3-1/221056/5 "2020-02-27T10:35:21Z")
correct solution:
1. stop all metricbeats clients
2. delete index in elasticsearch
3. run on one of metricbeats client: metricbeat setup -e -E output.elasticsearch.hosts=['10.130.10.40:9200'] -E setup.kibana.host=10.130.10.40:5601
4. edit Index Lifecycle Policies
5. run all metricbeats clients
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 26, 2020, 10:35am UTC](https://discuss.elastic.co/t/metricbeat-dosen-t-shows-in-kibana-infrastructure-after-deleting-index-metricbeat-7-3-1/221056/6 "2020-03-26T10:35:28Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.