#Charts for nginx url wise logs
1 messages · Page 1 of 1 (latest)
I did manage to get status code, but have no idea on how to view latency charts.
# NGINX
# debian, arch
- name: nginx
path: /var/log/nginx/ncsa.log
url_patterns:
- name: mf
match: '*/mf*'
Above is my go.d/web_log.conf
access_log /var/log/nginx/ncsa.log timed_combined;
And this is my nginx log format
No, my doubt is for config, how to configure if I want each url seperately with latency
url patterns is a list, you configure a list of urls/patterns
Here is pattern sytanx doc: https://github.com/netdata/go.d.plugin/tree/master/pkg/matcher#supported-format. It is format expression. Your match parameter is invalid.
I believe it would be seen in the debug output, it was one of the reason I asked about it. It is always a good first step to debug the problem.
My match parameter works, but it is only showing charts for req/s and status codes.
Is there a way to get latency chart too.
you probably need VTS.
https://www.netdata.cloud/nginxvts-monitoring/
Learn everything about monitoring & troubleshooting NGINX VTS, what metrics are important to monitor and why, and how to monitor NGINX VTS with Netdata.
No, this isn't what I mean, suppose I have 10 urls which proxy through nginx, I need latency, status code, etc for those urls.
I have around 1000 such urls, so pattern for each of those is difficult to maintain.
yes, but look at https://learn.netdata.cloud/docs/data-collection/web-servers-and-web-proxies/nginx
it doesn't show you status codes or "latency" that's why i'm saying you need VTS.
https://learn.netdata.cloud/docs/data-collection/web-servers-and-web-proxies/nginx-vts
it's a module to nginx you install and load.
I think there is no latency, because weblog doesn't parse request_time. In my initial comment I suggested using debug mode - it would show the problem - it shows current parser.
I ran with debug mode, but couldn't find any errors.
Also can I get every url seperately or I have to add patterns for each url ?
it is not per URL, but per pattern. The debug mode shows the pattern is will use for logs parsing. My guess that the pattern doesn't have request_time. Can you share the debug output?