rn ^host.*$
>
>
> key zone
> pattern ^zone.*\ $
>
> …..
>
>
>
> then use record_trasformer type, to make further modifications. But, I
> didn’t tried above,
> probably it’s something that better to be asked from fluentd community..
>
>
>
quot; : \"%s\",",a[1], a[2]
printf "\"%s\" : \"%s\",",b[1], b[2]
#printf "%s",$3 ","
#printf "%s",$5 ","
#printf "%s",$4 ","
printf "\"%s\" : %s,",c[1], c[
; /tmp/test.awk
> { client: xx.xx.xx.xx server: www.xyz.com host: www.xyz.com request: GET
> /api/xyz HTTP/1.1reason: limiting connections by zone "rl_conn"
> }
>
>
> br,
> Aziz.
>
>
>
>
>
> > On 10 Jan 2018, at 14:45, mohit Agrawal wrote:
> &
wrote:
> Hi Mohit,
>
> check the second reply. I’m not sure that there is a conventional pretty
> printing
> tools for nginx error log.
>
>
> br,
> Aziz.
>
>
>
>
>
> > On 10 Jan 2018, at 14:37, mohit Agrawal wrote:
> >
> > Hi Aziz,
> >
the your questing, it looks like you need something
> like logstash grok filter.
>
> br,
> Aziz.
>
>
>
>
>
> > On 10 Jan 2018, at 11:45, mohit Agrawal wrote:
> >
> > Hi ,
> >
> > I am looking to parse nginx error log so as to find out whi
HTTP/1.1", reason: "limiting connections by
zone "rl_conn""}
so that I can pass it through ELK stack and find out the root ip which is
causing issue.
--
Mohit Agrawal
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx