Comments on: Pro tip – define your log repository as a Chrome Custom Search Engine http://v1.ripper234.com/p/pro-tip-define-your-log-repository-as-a-chrome-custom-search-engine/ Stuff Ron Gross Finds Interesting Sun, 02 Aug 2015 11:03:35 +0000 hourly 1 https://wordpress.org/?v=4.5.3 By: ripper234 http://v1.ripper234.com/p/pro-tip-define-your-log-repository-as-a-chrome-custom-search-engine/comment-page-1/#comment-10867 Fri, 09 Aug 2013 07:35:02 +0000 http://v1.ripper234.com/?p=1918#comment-10867 @Elazar – this post isn’t about choosing yuor log framework (we already use Splunk at CommerceSciences and have no reason to switch – it’s working great for us).

Also, you always get production errors that don’t show up on integration tests … it’s an entirely different post to discuss “how much integration testing is enough”

]]> By: Elazar Leibovich http://v1.ripper234.com/p/pro-tip-define-your-log-repository-as-a-chrome-custom-search-engine/comment-page-1/#comment-10824 Thu, 08 Aug 2013 12:54:35 +0000 http://v1.ripper234.com/?p=1918#comment-10824 Try logstash and graylog2. I heard splunk could be expensive.

Also, I’ll fail the integration tests if any warning or error occured during normal uses.

]]>