We covered this topic quite extensively on the Takipi blog. Grepping through huge unstructured text is quite frustrating. Sumo Logic, Graylog, Loggly, PaperTra

We covered this topic quite extensively on the Takipi blog. Grepping through huge unstructured text is quite frustrating. Sumo Logic, Graylog, Loggly, PaperTrail, Logentries, Stackify: http://blog.takipi.com/how-to-choose-the-right-log-management-tool/ http://blog.takipi.com/how-to-choose-the-right-log-managemen... ELK vs Splunk: http://blog.takipi.com/splunk-vs-elk-the-log-management-tools-decision-making-guide/ http://blog.takipi.com/splunk-vs-elk-the-log-management-tool... Hosted ELK tools: http://blog.takipi.com/hosted-elasticsearch-the-future-of-your-elk-stack/ http://blog.takipi.com/hosted-elasticsearch-the-future-of-yo... We're actually building (and using) a log alternative called OverOps (https://www.overops.com https://www.overops.com), it's a native JVM agent that adds links to each log warning / error / exception that lead to the actual variable state and code that caused them, across the entire call stack. Disclaimer: I work there, would be happy to answer any question.