The danger of using a size based rollover (unless you set the size and log rollover to be fairly high) is that in case of problems, the actual cause of the problem might get rolled off the end by the time you get to it (kafka can be very chatty in some kinds of failure cases). That is probably the biggest reason for a date-rolling log...
On the other hand, the date-rolling can leave a lot of cruft around if you do not have a cleaner process running on a periodic basis...
Dave DeMaagd [EMAIL PROTECTED] | 818 262 7958
([EMAIL PROTECTED] - Mon, Jul 01, 2013 at 11:26:24AM -0700)
Thanks On Mon, Jul 1, 2013 at 11:44 AM, David DeMaagd <[EMAIL PROTECTED]>wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext