What is the benefit of using Logstash over indexing directly into
Elasticsearch?
I have all of my data that needs indexing going into a queue. At the moment
I have a small program that gets the messages from the queue and adds them
into Elasticsearch.
How would this be different if I were to use Logstash, and what would be
the pros and cons for indexing directly into Elasticsearch vs using
Logstash?
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d65d3fbe-6d91-488f-a5cb-f91e0d07d5fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Mainly the ability to parse log texts easily and restructure it as json
("grok")
There's no "better" way really, if your app knows what it's doing and you
use batching and have proper error recovery its probably better to have it
that way
--
Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer & Consultant
Author of RavenDB in Action http://manning.com/synhershko/
On Wed, Sep 24, 2014 at 2:29 PM, Andrew Rimmer andrew@outofmemory.co.uk
wrote:
What is the benefit of using Logstash over indexing directly into
Elasticsearch?
I have all of my data that needs indexing going into a queue. At the
moment I have a small program that gets the messages from the queue and
adds them into Elasticsearch.
How would this be different if I were to use Logstash, and what would be
the pros and cons for indexing directly into Elasticsearch vs using
Logstash?
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/d65d3fbe-6d91-488f-a5cb-f91e0d07d5fb%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/d65d3fbe-6d91-488f-a5cb-f91e0d07d5fb%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZtibdkOP1_-QPFDaTZ1iBhZrK2W1M9SUacx%2B2J_AhwoDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
So I am not losing out on anything by using my own service to write
directly to Elasticsearch, that is good to know. My data already serializes
nicely into json, so there isn't really much effort into preparing it for
indexing in Elasticsearch.
On 24 September 2014 12:32, Itamar Syn-Hershko itamar@code972.com wrote:
Mainly the ability to parse log texts easily and restructure it as json
("grok")
There's no "better" way really, if your app knows what it's doing and you
use batching and have proper error recovery its probably better to have it
that way
--
Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer & Consultant
Author of RavenDB in Action http://manning.com/synhershko/
On Wed, Sep 24, 2014 at 2:29 PM, Andrew Rimmer andrew@outofmemory.co.uk
wrote:
What is the benefit of using Logstash over indexing directly into
Elasticsearch?
I have all of my data that needs indexing going into a queue. At the
moment I have a small program that gets the messages from the queue and
adds them into Elasticsearch.
How would this be different if I were to use Logstash, and what would be
the pros and cons for indexing directly into Elasticsearch vs using
Logstash?
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/d65d3fbe-6d91-488f-a5cb-f91e0d07d5fb%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/d65d3fbe-6d91-488f-a5cb-f91e0d07d5fb%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/bhuBUIaZMoU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZtibdkOP1_-QPFDaTZ1iBhZrK2W1M9SUacx%2B2J_AhwoDA%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZtibdkOP1_-QPFDaTZ1iBhZrK2W1M9SUacx%2B2J_AhwoDA%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CANHkSS3RnAVCibceiRr-Z7nW4O_QuOUy1zA1xQqca059g%3DbSKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.