This is a bit of a kludge, but I've been tracking these in my nginx access
log. I have nginx in front of varnish, primarily to gzip (at one point, ESI
and gzip were incompatible). Nginx captures extra headers output by varnish
and write them to its own log.
example nginx log config line:
log_format main '$host $remote_addr - $remote_user [$time_local]
"$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"
$upstream_response_time $upstream_http_x_cache';
On Fri, Oct 8, 2010 at 11:10 AM, Angelo Höngens <[email protected]>wrote:
> On 8-10-2010 18:59, Caunter, Stefan wrote:
> > Hit/miss is a vcl addition to vcl_deliver:
> >
> > sub vcl_deliver {
> > ..
>
> Stefan,
>
> Thanks for your response. I know I can output the hit/miss in the
> response headers (I already do), but I want the extra fields (time taken
> and 'action') in the varnishncsa output. I write all varnishncsa output
> of all nodes to a central logging server, and we want to do analysis on
> those log files later.
>
> Angelo.
>
>
>
>
>
> _______________________________________________
> varnish-misc mailing list
> [email protected]
> http://lists.varnish-cache.org/mailman/listinfo/varnish-misc
>
_______________________________________________
varnish-misc mailing list
[email protected]
http://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
