Loggly cannot accept our SOLR queries as fast as we get them in production. We get 2.5M lines of queries in the log file per every 10 minutes, and to send to Loggly it takes literally 1.5 hours even when having 20 Hadoop servers sending them.
What we really need from Loggly is a way to point Loggly at an S3 log file and have Loggly load it in. On Sun, Aug 11, 2013 at 8:57 AM, Shreejay Nair <shreej...@gmail.com> wrote: > There are a lot of tools out there with varying degrees of functionality ( > and ease of setup) we also have multiple solr servers in production ( both > cloud and single nodes ) and we have decided to use > http://loggly. <http://loggly.com/> We will probably be setting it up for > all our servers in the next few weeks. . > > There are plenty of other such log analysis tools. It all depends on your > particular use case. > > --Shreejay > > > > On Sunday, August 11, 2013, adfel70 wrote: > > > Hi > > I'm looking at a tool that could help me perform solr logging analysis. > > I use SolrCloud on multiple servers, so the tool should be able to > collect > > logs from multiple servers. > > > > Any tool you use and can advice of? > > > > Thanks > > > > > > > > -- > > View this message in context: > > > http://lucene.472066.n3.nabble.com/What-do-you-use-for-solr-s-logging-analysis-tp4083809.html > > Sent from the Solr - User mailing list archive at Nabble.com. > > > > > -- > -- > Shreejay Nair > Sent from my mobile device. Please excuse brevity and typos. > -- Bill Bell billnb...@gmail.com cell 720-256-8076
