Find a particular request and its relative url
If you need to find the url that serves a particular requests, i.e.: 400, you can try running this on the varnish server: varnishlog -i RxURL,TxStatus | tee…
#Varnish
Check which server is serving the content from
while true; do curl -s -I http://www.example.com/ | egrep Varnish-Host\|X-Cache | egrep –color pres\|X-Cache; done
Warm up a server (populate cache)
If you need to start a server, you might want to populate it first with some content, before putting it live to the public wget –no-directories –recursive –level…
A general Varnish health check.
From Varnsih documentation it is quite clear that Varnishstat gives a good representation of the general health of Varnish, including cache hit rate, uptime, number of failed backend…
Useful varnishlog commands
varnishtop -i TxStatus Log client requests (you can also add :503 to check only for 503 being returned to a client varnishncsa -F "%r %s" | grep "…
Find the least cached URIs
To improve your cache hit ratio, the best thing to do is to use varnishtop to see the URIs that are the most often fetched from the back…
Fetch the data through Varnish
GET -Used http://localhost:80/ HEAD and GET are the same lwp-request tool. HEAD replies with HTTP headers, while GET returns everything. In this case: -U prints the request headers…