Hi guys,
I have this configured in my web_log.conf:
nginx_log:
name: ‘nginx’
path: ‘/var/log/nginx/access.log’
categories:
CheckMapping : ‘CheckMapping.’
UploadLog : 'UploadLog.’
These words are part of a query string. What am i doing wrong that netdata does not show categories ?
Thank you!
Hey @alen-loncaric,
Did you make it work? Please tell us if you need any further assistance!
You can disable python modules in python.d.conf, go modules in go.d.conf
cd to netdata user dir (usually it is /etc/netdata or /opt/netdata/etc/netdata depends on your install)
as root user
./edit-config python.d.conf
there
web_log: no
Before ensure your go weblog is correctly configured
https://github.com/netdata/go.d.plugin/tree/master/modules/weblog#troubleshooting
Guys i have disabled web_log in python.d and enabled go.d web_log
The dashboard is still showing python.d weblog. How can i remove it and use go.d weblog?
@ilyam8 there isnt any request per chart :S
How do i diasable python weblog and enable golang ?
Why are there two versions ?
'*CheckMapping.*' is the same as 'CheckMapping', but slower.
weblog uses re.search
Scan through string looking for the first location where the regular expression pattern produces a match …
The config looks valid and i would expect to see Requests Per Url chart on the dashboard.
And i suggest to switch to golang version of weblog
Probably this editor cutted out the stars but i am using .*CheckMapping.*
nginx_log: name: 'nginx' path: '/var/log/nginx/access.log' categories: checkmapping : '.*CheckMapping.*'
Can you please test .*CheckMapping.*
conf is pretty much default:
# netdata python.d.plugin configuration for web log
#
# This file is in YaML format. Generally the format is:
#
# name: value
#
# There are 2 sections:
# - global variables
# - one or more JOBS
#
# JOBS allow you to collect values from multiple sources.
# Each source will have its own set of charts.
#
# JOB parameters have to be indented (using spaces only, example below).
# ----------------------------------------------------------------------
# Global Variables
# These variables set the defaults for all JOBs, however each JOB
# may define its own, overriding the defaults.
# update_every sets the default data collection frequency.
# If unset, the python.d.plugin default is used.
# update_every: 1
# priority controls the order of charts at the netdata dashboard.
# Lower numbers move the charts towards the top of the page.
# If unset, the default for python.d.plugin is used.
# priority: 60000
# penalty indicates whether to apply penalty to update_every in case of failures.
# Penalty will increase every 5 failed updates in a row. Maximum penalty is 10 minutes.
# penalty: yes
# autodetection_retry sets the job re-check interval in seconds.
# The job is not deleted if check fails.
# Attempts to start the job are made once every autodetection_retry.
# This feature is disabled by default.
# autodetection_retry: 0
# ----------------------------------------------------------------------
# JOBS (data collection sources)
#
# The default JOBS share the same *name*. JOBS with the same name
# are mutually exclusive. Only one of them will be allowed running at
# any time. This allows autodetection to try several alternatives and
# pick the one that works.
#
# Any number of jobs is supported.
# ----------------------------------------------------------------------
# PLUGIN CONFIGURATION
#
# All python.d.plugin JOBS (for all its modules) support a set of
# predefined parameters. These are:
#
# job_name:
# name: myname # the JOB's name as it will appear at the
# # dashboard (by default is the job_name)
# # JOBs sharing a name are mutually exclusive
# update_every: 1 # the JOB's data collection frequency
# priority: 60000 # the JOB's order on the dashboard
# penalty: yes # the JOB's penalty
# autodetection_retry: 0 # the JOB's re-check interval in seconds
#
# Additionally to the above, web_log also supports the following:
#
# path: 'PATH' # the path to web server log file
# path: 'PATH[0-9]*[0-9]' # log files with date suffix are also supported
# detailed_response_codes: yes/no # default: yes. Additional chart where response codes are not grouped
# detailed_response_aggregate: yes/no # default: yes. Not aggregated detailed response codes charts
# all_time : yes/no # default: yes. All time unique client IPs chart (50000 addresses ~ 400KB)
# filter: # filter with regex
# include: 'REGEX' # only those rows that matches the regex
# exclude: 'REGEX' # all rows except those that matches the regex
# categories: # requests per url chart configuration
# cacti: 'cacti.*' # name(dimension): REGEX to match
# observium: 'observium.*' # name(dimension): REGEX to match
# stub_status: 'stub_status' # name(dimension): REGEX to match
# user_defined: # requests per pattern in <user_defined> field (custom_log_format)
# cacti: 'cacti.*' # name(dimension): REGEX to match
# observium: 'observium.*' # name(dimension): REGEX to match
# stub_status: 'stub_status' # name(dimension): REGEX to match
# custom_log_format: # define a custom log format
# pattern: '(?P<address>[\da-f.:]+) -.*?"(?P<method>[A-Z]+) (?P<url>.*?)" (?P<code>[1-9]\d{2}) (?P<bytes_sent>\d+) (?P<resp_length>\d+) (?P<resp_time>\d+\.\d+) '
# time_multiplier: 1000000 # type <int>/<float> - convert time to microseconds
# histogram: [1,3,10,30,100, ...] # type list of int - Cumulative histogram of response time in milli seconds
# ----------------------------------------------------------------------
# WEB SERVER CONFIGURATION
#
# Make sure the web server log directory and the web server log files
# can be read by user 'netdata'.
#
# To enable the timings chart and the requests size dimension, the
# web server needs to log them. This is how to add them:
#
# nginx:
# log_format netdata '$remote_addr - $remote_user [$time_local] '
# '"$request" $status $body_bytes_sent '
# '$request_length $request_time $upstream_response_time '
# '"$http_referer" "$http_user_agent"';
# access_log /var/log/nginx/access.log netdata;
#
# apache (you need mod_logio enabled):
# LogFormat "%h %l %u %t \"%r\" %>s %O %I %D \"%{Referer}i\" \"%{User-Agent}i\"" vhost_netdata
# LogFormat "%h %l %u %t \"%r\" %>s %O %I %D \"%{Referer}i\" \"%{User-Agent}i\"" netdata
# CustomLog "/var/log/apache2/access.log" netdata
# ----------------------------------------------------------------------
# VHOST AND PORT
# if your want to graph the request/sec per virtual host and per port (to check the number of requests in http vs https)
# in apache : (%v gives the hostname, %p the port number)
# LogFormat "%v %p %h %t \"%r\" %>s %O %I %D \"%{Referer}i\" \"%{User-Agent}i\"" vhost_netdata
#
# and in this file in apache_vhosts_log section, add :
# custom_log_format:
# pattern: '(?P<vhost>[a-zA-Z\d.-_]+) (?P<port>\d+) (?P<address>[\da-f.:]+) \[.*\] "(?P<method>[A-Z]+)[^"]*" (?P<code>[1-9]\d{2}) (?P<bytes_sent>\d+) (?P<resp_length>\d+) (?P<resp_time>\d+)'
# in nginx: ($host or $http_host give the hostname, $server_port the port number)
# log_format netdatavhost '$host $server_port $remote_addr - $remote_user [$time_local] '
# '"$request" $status $body_bytes_sent '
# '$request_length $request_time $upstream_response_time '
# '"$http_referer" "$http_user_agent"';
#
# access_log /var/log/nginx/access.log netdatavhost;
#
# be aware that the access_log directive in a server{} block overwrites the one in http{}, if your vhosts have individual log
# files, you have to specify the general netdata log in each vhost as a second access_log statement.
#
# and in this file in nginx_log section, add :
# custom_log_format:
# pattern: '(?P<vhost>[a-zA-Z\d.-_\[\]]+) (?P<port>\d+) (?P<address>[\da-f.:]+) .* "(?P<method>[A-Z]+)[^"]*" (?P<code>[1-9]\d{2}) (?P<bytes_sent>\d+) (?P<resp_length>\d+) (?P<resp_time>\d+)'
# ----------------------------------------------------------------------
# AUTO-DETECTION JOBS
# only one of them per web server will run (when they have the same name)
# -------------------------------------------
# nginx log on various distros
# debian, arch
nginx_log:
name: 'nginx'
path: '/var/log/nginx/access.log'
categories:
checkmapping : '.*CheckMapping.*'
# gentoo
nginx_log2:
name: 'nginx'
path: '/var/log/nginx/localhost.access_log'
# -------------------------------------------
# apache log on various distros
# debian
apache_log:
name: 'apache'
path: '/var/log/apache2/access.log'
# gentoo
apache_log2:
name: 'apache'
path: '/var/log/apache2/access_log'
# arch
apache_log3:
name: 'apache'
path: '/var/log/httpd/access_log'
# debian
apache_vhosts_log:
name: 'apache_vhosts'
path: '/var/log/apache2/other_vhosts_access.log'
# -------------------------------------------
# gunicorn log on various distros
gunicorn_log:
name: 'gunicorn'
path: '/var/log/gunicorn/access.log'
gunicorn_log2:
name: 'gunicorn'
path: '/var/log/gunicorn/gunicorn-access.log'
# -------------------------------------------
# Apache Cache
apache_cache:
name: 'apache_cache'
type: 'apache_cache'
path: '/var/log/apache/cache.log'
apache2_cache:
name: 'apache_cache'
type: 'apache_cache'
path: '/var/log/apache2/cache.log'
httpd_cache:
name: 'apache_cache'
type: 'apache_cache'
path: '/var/log/httpd/cache.log'
# -------------------------------------------
# Squid
# debian/ubuntu
squid_log1:
name: 'squid'
type: 'squid'
path: '/var/log/squid3/access.log'
#gentoo
squid_log2:
name: 'squid'
type: 'squid'
path: '/var/log/squid/access.log'
Ok i tested with this:
nginx_log:
name: ‘nginx’
path: ‘/var/log/nginx/access.log’
categories:
checkmapping : ‘.CheckMapping.’
from access log:
xx.xx.xx.xxx - - [06/Nov/2020:09:22:35 +0100] “POST /test/Interface.ashx?o=CheckMapping&&sn=1223434234 HTTP/1.1” 200 156 301 0.002 0.001 “-” “client1243”
So this request should go to checkmapping category ? Correct?
Well it is not 
Capture — ImgBB ?
Why?
Let’s check
And make sure you have correct indentation.
Show your web_log.conf
cat web_log.conf
Hey,
I tested .*UploadLog.* on https://regex101.com/ and it matches the test URL you provided. Can you test this out and update us with the results?
Even if I use ‘UploadLog.*’ REGEX
AND on test http://google.com/UploadLog.php?/****** It does not match
Anyone has any example… how it should work
Hey @ilyam8,
Thanks for chiming in. I saw that the configuration mentions that it accepts REGEX only. it doesn’t support the matcher helper function?
Hi
Are you sure about . at the end?
And make sure you have correct indentation.
nginx_log:
name: nginx
path: '/var/log/nginx/access.log'
categories:
CheckMapping: 'CheckMapping.'
UploadLog: 'UploadLog.'
Hi all,
Have you resolved this topic? Because we are facing an issue with nginx plus (r25) and web_log.conf for both plugins, go.d and python.d (we tried to configure many nginx logs to them both), and we cannot see the logs from nginx server blocks in netdata.
Have you any idea for this issue?
Hi, @nmarantos. If there is an issue, I would recommend starting with running the plugin in debug mode. If you share it I will be able to help you.
Hi @ilyam8, the following is the debug mode for go.d.plugin web_log
[ DEBUG ] main[main] main.go:111 plugin: name=go.d, version=v0.28.2
[ DEBUG ] main[main] main.go:113 current user: name=netdata, uid=116
[ INFO ] main[main] agent.go:106 instance is started
[ INFO ] main[main] setup.go:39 loading config file
[ INFO ] main[main] setup.go:47 looking for ‘go.d.conf’ in [/etc/netdata /usr/lib/netdata/conf.d]
[ INFO ] main[main] setup.go:54 found ‘/etc/netdata/go.d.conf
[ INFO ] main[main] setup.go:61 config successfully loaded
[ INFO ] main[main] agent.go:110 using config: enabled ‘true’, default_run ‘true’, max_procs ‘0’
[ INFO ] main[main] setup.go:66 loading modules
[ INFO ] main[main] setup.go:85 enabled/registered modules: 1/59
[ INFO ] main[main] setup.go:90 building discovery config
[ INFO ] main[main] setup.go:116 looking for ‘web_log.conf’ in [/etc/netdata/go.d /usr/lib/netdata/conf.d/go.d]
[ INFO ] main[main] setup.go:123 found ‘/etc/netdata/go.d/web_log.conf
[ INFO ] main[main] setup.go:128 dummy/read/watch paths: 0/1/0
[ INFO ] discovery[manager] manager.go:90 registered discoverers: [file discovery: [file reader]]
[ INFO ] discovery[manager] manager.go:95 instance is started
[ INFO ] run[manager] run.go:30 instance is started
[ INFO ] discovery[file manager] discovery.go:71 instance is started
[ INFO ] build[manager] build.go:106 instance is started
[ INFO ] discovery[file reader] read.go:39 instance is started
[ INFO ] discovery[file reader] read.go:40 instance is stopped
[ DEBUG ] build[manager] build.go:153 received config group (’/etc/netdata/go.d/web_log.conf’): 0 jobs (added: 0, removed: 0)
[ DEBUG ] run[manager] run.go:41 tick 0
[ DEBUG ] run[manager] run.go:41 tick 1
[ DEBUG ] run[manager] run.go:41 tick 2
[ DEBUG ] run[manager] run.go:41 tick 3
[ DEBUG ] run[manager] run.go:41 tick 4
[ DEBUG ] run[manager] run.go:41 tick 5
[ DEBUG ] run[manager] run.go:41 tick 6
[ DEBUG ] run[manager] run.go:41 tick 7
[ DEBUG ] run[manager] run.go:41 tick 8
[ DEBUG ] run[manager] run.go:41 tick 9
[ DEBUG ] run[manager] run.go:41 tick 10
[ DEBUG ] run[manager] run.go:41 tick 11
[ DEBUG ] run[manager] run.go:41 tick 12
[ DEBUG ] run[manager] run.go:41 tick 13
[ DEBUG ] run[manager] run.go:41 tick 14
[ DEBUG ] run[manager] run.go:41 tick 15
[ DEBUG ] run[manager] run.go:41 tick 16
^C[ INFO ] main[main] agent.go:191 received interrupt signal (2). Terminating…
It says /etc/netdata/go.d/web_log.conf has 0 configured jobs, let’s see the following:
ls -l /etc/netdata/go.d/web_log.conf
cat /etc/netdata/go.d/web_log.conf
i tried with the following configuration, the simple, with log_type: auto and with log_type: csv, format our access_log format. All without success and the same result 0 configured jobs.
My configuration has not the default /var/log/nginx/access.log but /var/log/nginx/master.access.log
Nginx Plus - go.d/web_log.conf
jobs:
- name: nginx_master
path: /var/log/nginx/master.access.log
We had the same results when we configured it with python module, while with the same config for python module in nginx open source it works properly with 15 configs.
Nginx open source - python.d/web_log.conf
nginx_log:
name: 'nginx_master'
path: '/var/log/nginx/master.access.log'