Chasing 503 Guru's

[Ross Brown]

-----Original Message-----
From: varnish-misc-bounces at varnish-cache.org [mailto:varnish-misc-bounces at varnish-cache.org] On Behalf Of Simon Males
Sent: Friday, 3 December 2010 3:30 a.m.
To: Per Buer
Cc: varnish-misc at projects.linpro.no
Subject: Re: Chasing 503 Guru's

>>> Or is it common practice to write varnishlog to disk in production environments?
>>
>> No. On Linux the vm get's slightly dazzled by all the IO and will
>> behave strangely. You can instruct varnishlog to only log 503's. That
>> might be ideal for you.

> I'm not sure how to do this. The closest I get is:
> varnishlog -o -i TxStatus -I 503
>
> Though that doesn't return the whole entry.

You could try something like this, which takes inspiration from something I found on Tollef's blog ( http://err.no/personal/blog/2008/Dec/17#2008-12-17-10-14_poor_mans_filtering_language )

varnishlog -o | perl -ne 'BEGIN { $/ = "";} print if (/TxStatus.*(50\d)/);'


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20101207/efd1fbd9/attachment-0003.html>