I finally end up writing my own error log fluentd custom parser in ruby.
It's working now.
Thanks for help anyways, much appreciated
On 11 January 2018 at 14:26, Aziz Rozyev wrote:
> Hi,
>
> seems, that fluentd has an nginx_parser plugin already, another solution
> that probably should work is
Hi,
seems, that fluentd has an nginx_parser plugin already, another solution that
probably should work is to use the grep filters,
something as follows:
@type grep
key client
patter ^client.*\ $
key server
pattern ^server.*\ $
key host
Hi All,
I have something like this. I tested the `tail -f /var/log/nginx/error.log
| awk -f /var/log/nginx/test.awk` part and it just works fine. But when i
try to run it through fluentd, it doesn't do anything. Any idea why ?
@type exec
format json
tag sample
comm
Aziz Rozyev Wrote:
---
> Hi Mohit,
>
> check the second reply. I’m not sure that there is a conventional
> pretty printing
> tools for nginx error log.
Look at awstats.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,278065,278080#ms
Thanks Aziz for this, I get your point, but can we do awking in fluentd
cons file ? Basically we are looking for realtime awking a nginx error log
file, how heavy this would be according to you.
On 10 January 2018 at 17:44, Aziz Rozyev wrote:
> If you need parse exactly the same format, as you’v
If you need parse exactly the same format, as you’ve shown in you question,
it’s fairly easy to create something e.g. perl/awk/sed script.
for instance:
# tst.awk #
BEGIN {FS = "," }
{
split($1, m, "\ ")
printf "%s", "{ "
printf "%s",$2
printf "%s
Yeah I have tried grok / regex pattern as well. But not extensive success
that I achieved. grok didn't work for me, I tried regex then it was able to
segregate time , pid, tid, log_level and message. I also need message break
up for above pattern
On 10 January 2018 at 17:12, Aziz Rozyev 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,
>
> log_format directive only provides formatting for access log, I am looking to
> format erro
Hi Aziz,
log_format directive only provides formatting for access log, I am looking
to format error.log which doesn't take log_format directive.
Above example that I gave is just for nginx error logs.
Thanks
On 10 January 2018 at 15:26, Aziz Rozyev wrote:
> btw, after re-reading the your quest
btw, after re-reading 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 which particular IP
> is throttled during specific amount o
is the 'log_format json’ is what you’re asking for?
http://nginx.org/en/docs/http/ngx_http_log_module.html#log_format
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 which particular IP
> is throttled during
Hi ,
I am looking to parse nginx error log so as to find out which particular IP
is throttled during specific amount of time on connection throttling /
request throttling. The format looks like :
2018/01/10 06:26:31 [error] 13485#13485: *64285471 limiting
connections by zone "rl_conn", client: x
12 matches
Mail list logo
