Helper tool that continuously reads an NGINX log file and exports metrics to Prometheus.
You can either use a simple configuration, using command-line flags, or create a configuration file with a more advanced configuration.
Use the command-line:
./prometheus-nginxlog-exporter \ -format="<FORMAT>" \ -listen-port=4040 \ -namespace=nginx \ [PATHS-TO-LOGFILES...]
Use the configuration file:
./prometheus-nginxlog-exporter -config-file /path/to/config.hcl
This exporter collects the following metrics. This collector can listen on
multiple log files at once and publish metrics in different namespaces. Each
metric uses the labels method (containing the HTTP request method) and
status (containing the HTTP status code).
|
❗
|
Keep in mind that some of these metrics will require certain values to be present
in your access log format (for example, the |
Metrics are exported at the /metrics path.
These metrics are exported:
|
The total amount of processed HTTP requests/responses. |
|
The total amount of transferred content in bytes. |
|
A summary vector of the upstream response times in seconds. Logging these needs to be specifically enabled in NGINX using the |
|
Same as |
|
A summary vector of the total response times in seconds. Logging these needs to be specifically enabled in NGINX using the |
|
Same as |
Additional labels can be configured in the configuration file (see below).
You can specify a configuration file to read at startup. The configuration file is expected to be either in HCL or YAML format. Here’s an example file:
listen {
port = 4040
address = "10.1.2.3"
}
consul {
enable = true
address = "localhost:8500"
datacenter = "dc1"
scheme = "http"
token = ""
service {
id = "nginx-exporter"
name = "nginx-exporter"
tags = ["foo", "bar"]
}
}
namespace "app1" {
format = "$remote_addr - $remote_user [$time_local] \"$request\" $status $body_bytes_sent \"$http_referer\" \"$http_user_agent\" \"$http_x_forwarded_for\""
source_files = [
"/var/log/nginx/app1/access.log"
]
labels {
app = "application-one"
environment = "production"
foo = "bar"
}
}
namespace "app2" {
format = "$remote_addr - $remote_user [$time_local] \"$request\" $status $body_bytes_sent \"$http_referer\" \"$http_user_agent\" \"$http_x_forwarded_for\" $upstream_response_time"
source_files = [
"/var/log/nginx/app2/access.log"
]
}The same file as YAML file:
listen:
port: 4040
address: "10.1.2.3"
consul:
enable: true
address: "localhost:8500"
datacenter: dc1
scheme: http
token: ""
service:
id: "nginx-exporter"
name: "nginx-exporter"
tags: ["foo", "bar"]
namespaces:
- name: app1
format: "$remote_addr - $remote_user [$time_local] \"$request\" $status $body_bytes_sent \"$http_referer\" \"$http_user_agent\" \"$http_x_forwarded_for\""
source_files:
- /var/log/nginx/app1/access.log
labels:
app: "application-one"
environment: "production"
foo: "bar"
- name: app2
format: "$remote_addr - $remote_user [$time_local] \"$request\" $status $body_bytes_sent \"$http_referer\" \"$http_user_agent\" \"$http_x_forwarded_for\" $upstream_response_time"
source_files:
- /var/log/nginx/app2/access.logThe exporter contains features that are currently experimental and may change without prior notice.
To use these features, either set the -enable-experimental flag or add a enable_experimental option
to your configuration file.
Re-labeling lets you add arbitrary fields from the parsed log line as labels to your metrics.
To add a dynamic label, add a relabel statement to your configuration file:
namespace "app-1" {
// ...
relabel "host" {
from = "server_name"
whitelist = [ (1)
"host-a.com",
"host-b.de"
]
}
}-
The
whitelistproperty is optional; if set, only the supplied values will be added as label. All other values will be subsumed under the"other"label value. See #16 for a more detailed discussion around the reasoning.
Dynamic relabeling also allows you to aggregate your metrics by request path (which replaces the experimental feature originally introduced in #23):
namespace "app1" {
// ...
relabel "request_uri" {
from = "request"
split = 2
match "^/users/[0-9]+" {
replacement = "/users/:id"
}
match "^/profile" {
replacement = "/profile"
}
}
}The YAML configuration for relabelings works similar to the HCL configuration:
namespaces:
- name: app1
relabel_configs:
- target_label: request_uri
from: request
split: 2
matches:
- regexp: "^/users/[0-9]+"
replacement: "/users/:id"If your regular expression contains groups, you can also use the matched values of those in the replacement value:
relabel "request_uri" {
from = "request"
split = 2
match "^/(users|profiles)/[0-9]+" {
replacement = "/$1/:id"
}
}You can find an example unit file for this service in this repository. Simply copy the unit file to /etc/systemd/system:
$ wget -O /etc/systemd/system/prometheus-nginxlog-exporter.service https://raw.githubusercontent.com/martin-helmich/prometheus-nginxlog-exporter/master/systemd/prometheus-nginxlog-exporter.service $ systemctl enable prometheus-nginxlog-exporter $ systemctl start prometheus-nginxlog-exporter
The shipped unit file expects the binary to be located in /usr/local/bin/prometheus-nginxlog-exporter and the configuration file in /etc/prometheus-nginxlog-exporter.hcl. Adjust to your own needs.
You can also run this exporter from the Docker image quay.io/martinhelmich/prometheus-nginxlog-exporter:
$ docker run --name nginx-exporter -v logs:/mnt/nginxlogs -p 4040:4040 quay.io/martinhelmich/prometheus-nginxlog-exporter mnt/nginxlogs/access.log
Command-line flags and arguments can simply be appended to the docker run command, for example to use a
configuration file:
$ docker run --name nginx-exporter -p 4040:4040 -v logs:/mnt/nginxlogs -v /path/to/config.hcl:/etc/prometheus-nginxlog-exporter.hcl quay.io/martinhelmich/prometheus-nginxlog-exporter -config-file /etc/prometheus-nginxlog-exporter.hcl
I have started the exporter, but it is not exporting any application-specific metrics!
This may have several issues:
-
Make sure that the access log files that your exporter is listening on are present. The exporter will exit with an error code if a file is present but cannot be opened (for example, due to bad permissions), but will wait for a file if it does not yet exist.
-
Make sure that the exporter can parse the lines from your access log files. Pay attention to the
<namespace>_parse_errors_totalmetric, which will indicate how many log lines could not be parsed.
The exporter exports the
<namespace>_http_response_count_totalmetric, but not [other metric that is mentioned in the README]!
Most metrics require certain values to be present in the access log files that are not present in the NGINX default configuration. Especially, make sure that the access log contains the $upstream_response_time, $request_time and/or $body_bytes_sent variables. These need to be enabled in the NGINX configuration (more precisely, the log_format setting) and then added to the format specified for the exporter.
How can I configure NGINX to export these variables?
Have a look at NGINX’s Logging and Monitoring guide. It contains some good examples that contain the $request_time and $upstream_response_time:
log_format upstream_time '$remote_addr - $remote_user [$time_local] '
'"$request" $status $body_bytes_sent '
'"$http_referer" "$http_user_agent"'
'rt=$request_time uct="$upstream_connect_time" uht="$upstream_header_time" urt="$upstream_response_time"';-
tail, MIT license
-
gonx, MIT license
-
Prometheus Go client library, Apache License
-
HashiCorp configuration language, Mozilla Public License