# Logstash config - elasticsearch to elasticsearch

**URL:** <https://discuss.elastic.co/t/logstash-config-elasticsearch-to-elasticsearch/108546>\
**Category:** Logstash\
**Created:** [November 21, 2017, 10:46am UTC](https://discuss.elastic.co/t/logstash-config-elasticsearch-to-elasticsearch/108546 "2017-11-21T10:46:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![giangra](https://avatars.discourse-cdn.com/v4/letter/g/e9c0ed/32.png) [@giangra](https://discuss.elastic.co/u/giangra)\
**Post date:** [November 21, 2017, 10:46am UTC](https://discuss.elastic.co/t/logstash-config-elasticsearch-to-elasticsearch/108546/1 "2017-11-21T10:46:26Z")

</div>

Goodmorning everyone,  
I need to know if there is a possibility to set elasticsearch as input (also as an output), parsing all the logs I had previously parsed with logstash.  
For example:  
I have parsed all my akamai logs with a logstash configuration. Now I need to reparse the same logs file changing index. For now I've configured my configuration file this way:

input {  
elasticsearch {  
hosts =\> ["[http://192.168.1.3:9200/](http://192.168.1.3:9200/)"]  
user =\> "elastic"  
password =\> "changeme"  
index =\> "akamai\_logs\*"  
query =\> '{ "query": { "match\_all": {} } }'  
size =\> 500  
scroll =\> "5m"  
docinfo =\> true  
}  
}  
output {  
elasticsearch {  
hosts =\> ["[http://192.168.1.3:9200/](http://192.168.1.3:9200/)"]  
user =\> "elastic"  
password =\> "changeme"  
index =\> "newindex"  
}  
stdout { codec =\> rubydebug }  
}

What am I doing wrong?

Thanks for the support!

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 21, 2017, 10:50am UTC](https://discuss.elastic.co/t/logstash-config-elasticsearch-to-elasticsearch/108546/2 "2017-11-21T10:50:15Z")

</div>

Have you considered using [the reindex API](https://www.elastic.co/guide/en/elasticsearch/reference/6.0/docs-reindex.html#reindex-from-remote) to reindex from remote?

---

<div class="post-metadata">

**Author:** ![giangra](https://avatars.discourse-cdn.com/v4/letter/g/e9c0ed/32.png) [@giangra](https://discuss.elastic.co/u/giangra)\
**Post date:** [November 21, 2017, 10:52am UTC](https://discuss.elastic.co/t/logstash-config-elasticsearch-to-elasticsearch/108546/3 "2017-11-21T10:52:03Z")

</div>

Yes, but for my purpose it's not the best solution. Because in the near future I need to parse elasticsearch logs indexed by Graylog.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 21, 2017, 10:54am UTC](https://discuss.elastic.co/t/logstash-config-elasticsearch-to-elasticsearch/108546/4 "2017-11-21T10:54:30Z")

</div>

I don't have any experience with Graylog. Why would that data pose a problem?

---

<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:** [December 19, 2017, 10:54am UTC](https://discuss.elastic.co/t/logstash-config-elasticsearch-to-elasticsearch/108546/5 "2017-12-19T10:54:46Z")

</div>

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