# How to make an index as the destination index to store the data

**URL:** <https://discuss.elastic.co/t/how-to-make-an-index-as-the-destination-index-to-store-the-data/100001>\
**Category:** Elasticsearch\
**Created:** [September 11, 2017, 5:41am UTC](https://discuss.elastic.co/t/how-to-make-an-index-as-the-destination-index-to-store-the-data/100001 "2017-09-11T05:41:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![fazi347](https://avatars.discourse-cdn.com/v4/letter/f/b5e925/32.png) [@fazi347](https://discuss.elastic.co/u/fazi347)\
**Post date:** [September 11, 2017, 5:41am UTC](https://discuss.elastic.co/t/how-to-make-an-index-as-the-destination-index-to-store-the-data/100001/1 "2017-09-11T05:41:01Z")

</div>

## I am using elasticsearch and kibana for displaying the logs. When i use logstash-\* index the logs are disapying in kibana but when i am using the index which i created is not displaying any data. Is there any option to make the new index as the destination index to store data in elasticsearch. i can copy data using reindex and new index is showing the copied data but not receiving any new data.

[]# curl -XGE [http://localhost:9200/\_cat/indices?v](http://localhost:9200/_cat/indices?v)  
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size  
yellow open logstash-2017.09.08 cS\_z3ruvRb2lFk8Z-y\_nww 5 1 116 0 128.1kb 128.1kb  
close issuepredtool 3mcGPLT7RKSeHslHlPua5w  
yellow open fluentd juxdqw3QRNmH0NyMp9ZNTw 5 1 108 0 100.3kb 100.3kb  
yellow open .kibana Z\_EGBqWFSn6wtdhc0mYDsg 1 1 4 0 18.3kb 18.3kb  
yellow open test 4DzRjVhhT8KoGTuOrkpSYA 5 1 1 4 4.6kb 4.6kb  
yellow open issuepredtool1 U4L2epxHTs-Ke8yLkF-OBQ 5 1 114 0 71.9kb 71.9kb

* * *

issuepredtool1 index which i created and for testing purpose i have copied the data from logstash-\* index using reindex and kibana displaying this data.

curl -XGE [http://localhost:9200/issuepredtool1](http://localhost:9200/issuepredtool1)  
{"issuepredtool1":{"aliases":{"fazi":{}},"mappings":{"fluentd":{"properties":{"@timestamp":{"type":"date"},"arguments":{"type":"text","fields":{"keyword":{"type":"keyword","ignore\_above":256}}},"issue":{"type":"text","fields":{"keyword":{"type":"keyword","ignore\_above":256}}},"issue\_category":{"type":"text","fields":{"keyword":{"type":"keyword","ignore\_above":256}}},"log\_id":{"type":"long"},"server\_name":{"type":"text","fields":{"keyword":{"type":"keyword","ignore\_above":256}}},"time\_stamp":{"type":"text","fields":{"keyword":{"type":"keyword","ignore\_above":256}}}}}},"settings":{"index":{"creation\_date":"1504880653564","number\_of\_shards":"5","number\_of\_replicas":"1","uuid":"U4L2epxHTs-Ke8yLkF-OBQ","version":{"created":"5050299"},"provided\_name":"issuepredtool1"}}}}

Please help to set the newly created index to receive data.  
Kibana and elasticsearch version 5.x

---

<div class="post-metadata">

**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\
**Post date:** [September 15, 2017, 8:28am UTC](https://discuss.elastic.co/t/how-to-make-an-index-as-the-destination-index-to-store-the-data/100001/2 "2017-09-15T08:28:09Z")

</div>

It looks like you are using logstash to ingest your data (that seems to be working). I have little experience in how to configure the [logstash output](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html), but I'm pretty sure this is the first place to look to change the index name your data gets send to. Sorry if I'm stating something obvious.

---

<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:** [October 13, 2017, 8:28am UTC](https://discuss.elastic.co/t/how-to-make-an-index-as-the-destination-index-to-store-the-data/100001/3 "2017-10-13T08:28:13Z")

</div>

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