-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 08/28/2014 05:42 PM, Jason Heffner wrote: > We are running Varnish 3.0.5-1 from the el6 repo. When trying to > use varnishlog with the -w option we are noticing that it ignores > the -m option. > > For instance > > varnishlog -a -w /var/log/varnish/varnish.log -m TxStatus:503
In my experience, -m in Varnish 3 does not filter at all unless you also provide -b or -c for backend or client transactions, respectively. It's unrelated to -w. Since you're evidently looking for client transactions including responses with status 503, try this: $ varnishlog -c -a -w /var/log/varnish/varnish.log -m TxStatus:503 (BTW, this has all been greatly improved in Varnish 4.) HTH, Geoff - -- ** * * UPLEX - Nils Goroll Systemoptimierung Scheffelstraße 32 22301 Hamburg Tel +49 40 2880 5731 Mob +49 176 636 90917 Fax +49 40 42949753 http://uplex.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJT/1YpAAoJEOUwvh9pJNURnLwP/3ugGQKcBlqCvg00Hy6/eaR6 5KugupgyQNCRNYqPuP0tykUJuDwqqoI+aF+RMa8N10AyW06yBCHuvqnxCmJ31GWp ohEVIOSsl5THcbCJHq9R6TWnOCnudC2kCB+QwdJATRbaNchlaJdwwEuigSNK1tQk mX9dyLG1FF2GQCVVPiQ3NtsZCQfkVlp6B/FSy1NZoDkiGrvr51hb/dJMokCyx7fv Zs1ci8HDITjX6dFms4WH+rzppvogaZj0fCbzhxlqkNWF+MnCAeMiyuiJT9oEayyN NUQWWz2gb9s24sN8SkVPLkMo1oSw9Wk4ZLYN/KstSe7EM1KAzeQ6le+wJigNOCwE xvqRsiMCyqoqo68rIFtfJunZYkxB0gpMpLHxGo9wk6/9mSxpPbI43rI8u8YiJCTb 79BVBmJXH4297tWksdawWJcfjDuSEqz5Wv7NYD/AI3lj519UFT0XLrmzzh80HiGg MGCJKtQD3k2XQvL8CxZ5ikQBXGhmFXcOox0LLvgwb9qH1TsfRCyQrcz73GJ7OBt4 yw2bniPzFF8bIirxpTv2VY9uNMLLe2Ua/g6IjWF109EfQiPcF/mmiuw49KKu57hQ cy20c3vB1UGlJlFvADoqLM5ImkgoQMkEiZVKNMwPl8aPFviJCCwkyjppevOv7oWV OIeJfXprjMHBTzXa3JhD =fJXN -----END PGP SIGNATURE----- _______________________________________________ varnish-misc mailing list varnish-misc@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc