http_log_module filter by status

[B.R.]

The documentation <http://wiki.nginx.org/HttpCoreModule#error_page> also
says that if you don't want to redirect to another page, you can use a
named redirection :
location / {
  error_page 404 @404;
}

location @404 {
  access_log /path/to/log;
}

The wiki syntax seems to be wrong though, since it is using brackets and
not braces.
---
*B. R.*


On Tue, Jun 12, 2012 at 4:08 PM, Maxim Dounin <mdounin at mdounin.ru> wrote:

> Hello!
>
> On Sun, Jun 10, 2012 at 01:40:12PM -0400, karlseguin wrote:
>
> > I was interested in having nginx log 404s to their own file.
> > Essentially, i _hate_ 404s, so I like to parse access logs find and
> > report all 404s. However, as-is, parsing large access logs can be quite
> > inefficient since 404s represent such a small % of the entire file. I
> > was thinking nginx could filter it out at write-time:
> >
> > access_log  not_found.log  combined buffer=16K 404;
> >
> >
> > Apologies for the lameness of the code, but this is what I came up
> > with:
> > https://gist.github.com/2906701
> >
> > I certainly don't recommend anyone uses it, I'm mostly just looking for
> > feedback. Is this better off in its own module? (there's so much code in
> > the http_log_module that I want to leverage though). There's much more
> > filtering that could go on that perhaps a new directive is a better
> > approach:
> >
> > access_log_filter $status /(40\d)/
> > access_log_filter $method GET
> >
> > (which is certainly beyond my capabilities).
> >
> > Thoughts?
>
> error_page 404 /404.html;
>
> location = /404.html {
>    access_log /path/to/log;
> }
>
> Maxim Dounin
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20120612/540ef383/attachment-0001.html>