Recommendation for varnishlog in production

[Guillaume Quintard]

1. use logrotate, or something like that
2. varnishlog is probably overkill for what you need, turn your gaze
towards varnishncsa
3. if you really want to use varnishlog, you should use '-q' to filter only
the "important" transactions (slow fetches/deliveries, errors, etc.)

-- 
Guillaume Quintard

On Mon, Sep 19, 2016 at 2:37 PM, Albert Tollkuçi <albert.tollkuci at gmail.com>
wrote:

> I've setup varnish as a proxy for a few websites and it's running
> smoothly. However I did notice that the log file is huge (daily size of
> around 100 GB). I guess that so much logging will hurt the performance and
> I'm looking at different options.
>
> I tried to remove -w filename option but this was required. Probably
> another option is to disable the service. However before making the changes
> I would like to ask if there's any recommendation of how to setup
> varnishlog in production server.
>
> Thank you,
> Albert
>
> --
> Web: http://www.tollkuci.com
> Follow me on: LinkedIn <http://www.linkedin.com/in/alberttollkuci> Google+
> <https://plus.google.com/+AlbertTollku%C3%A7i/posts> Facebook
> <https://www.facebook.com/albert.tollkuci> Twitter
> <https://twitter.com/AlbertTollkuci> Career 2.0
> <http://careers.stackoverflow.com/atollkuci>
> ------------------------------
>
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20160919/b4a7efdc/attachment.html>