Graphing number of 503s

Jason Heffner jdh132 at
Fri Oct 16 00:46:42 CEST 2015

I’d use varnishncsa as suggested below..

for v3 - returns any 429, 500, or 503 from varnish or front-end in log

DAEMON_OPTS="-a -f -w $logfile -D -m TxStatus:\"429|500|503\" -P $pidfile”

for v4 - returns any 429 only from varnish, and any above 500 to log

DAEMON_OPTS="-a -F '%{X-Forwarded-For}i %l %u %t "%r" %s %b "%{Referer}i" "%{User-agent}i"' -w $logfile -D -q \"RespStatus >= 429 or BerespStatus >= 500\" -P $pidfile"

Some common use examples I was using.


> On Oct 15, 2015, at 6:37 PM, Gabriel Filion <gabster at> wrote:
> On 15/10/15 03:00 PM, Per Buer wrote:
>>    I'd like to create a graph of how much 503 pages were served by varnish.
>>    Is there an easy way to count how much such error pages are sent to
>>    clients?
>> Sure. Throw Google Analytics at it and you'll have tons of graphs. Just
>> throw the GA stuff into the guru meditation page (Artur used this for
>> all sort of stuff).
> ah hmm actually this is not possible in this case since the varnish
> servers are used in front of shared hosting for a couple of select sites
> and we don't really control the contents of the sites.
> Guillaume's suggestion of using varnishncsa is a possibility that I can
> explore.
> While brainstorming with co-workers, we've had another idea too: since
> we're serving error pages as static html on one special backend we could
> inject a header in the request made to that server to identify the
> backend used in the original client request and thus count errors per
> backend.
> -- 
> Gabriel Filion
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at

More information about the varnish-misc mailing list