Hi, Logstash is the piece that first touches your logs, filters them, and then outputs them somewhere. People often use it with ElasticSearch. Once logs are in ES, they look at them with Kibana.
Note: somebody should write a Logstash output for Solr! In Solr world there is Flume, which has a Solr sink. Flume has file tailing capability and Cloudera's Morphlines should allow one to process the log much like Logstash filters let you process them. At Sematext we've built something called Logsene - http://sematext.com/logsene/ , which uses some of the above technologies or plays nice with them. Otis ---- Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm >________________________________ > From: Ivan Krišto <ivan.kri...@gmail.com> >To: java-user@lucene.apache.org >Cc: gudiseashok <gudise.as...@gmail.com> >Sent: Friday, September 20, 2013 1:59 AM >Subject: Re: Lucene for Log file indexing and search > > >On 09/19/2013 07:41 PM, gudiseashok wrote: >> I am learning lucene, I am developing an application do do a search in log >> files in multi-environment boxes, I have googled for the deeper >> understanding, but all examples were just referring for just field "File >> Name" & "Modification (i.e. fieldtypes associated with text search) and they >> are returning results. > >Hello! > >If you don't have some extremly specific needs checkout Logstash -- >http://logstash.net/ & http://www.elasticsearch.org/overview/logstash/ >It is powered by ElasticSearch (product similar to Solr, also based on >Lucene). > > > Regards, > Ivan Krišto > > >
