Forward Logs from Elasticsearch to external destination application

I'm looking to forward already stored logs from Elasticsearch to an external application-source.

We're quite aware that we could leverage Logstash to distribute/split the new future-incoming logs between Elasticsearch and other external destination BUT we would like to forward our already existing logs as-well.

Can anyone please suggest

Elasticsearch does not push data. It has a REST endpoint (pull).

You will need to use an additional tool take data from elasticsearch and push it to another destination.

Example, You can use Logstash with elasticsearch as an input and send data / documents to some other destination system.

There are many batch and streaming ETL tools that can use elasticsearch as a source.

1 Like

While waiting for the response, I did research and go through using Logstash & API's to export logs from Elasticsearch.

As per your response "There are many batch and streaming ETL tools that can use elasticsearch as a source."
@stephenb Can you please name few ETL tools that can help me achieve this objective? (Are you referring to queuing tools?)

Examples I have not looked close at each lately

Stream Sets
Elasticsearch has a JDBC connector so anything that reads JDBC.

Thanks for the response @stephenb
Considering that we would export the logs from Elasticsearch by any above means, doesn't this impose a overhead on the ELK-Stack? as this would be querying huge amount of data across all the indices

Well sure,

Like any datastore, reads / writes require some level of compute / IO resources nothing is free :slight_smile:

That is why often teams with this use case often split the ingest feed to elasticsearch to both elasticsearch and the other destination at ingest time.

Thank you @stephenb for your response/feedback.

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