The section seems to be less relevant than the one for saving metrics on a Prometheus server. Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
5.0 KiB
Enabling metrics and graphs for NginX logs (optional)
The playbook can install and configure the prometheus-nginxlog-exporter service for you, in order to make it possible to have some (visual) insight into nginx logs.
It will collect access logs from various nginx reverse-proxies which may be used internally (e.g. matrix-synapse-reverse-proxy-companion
, if Synapse workers are enabled) and will make them available at a Prometheus-compatible /metrics
endpoint.
See the project's documentation to learn what it does and why it might be useful to you.
Note: nginx is only used internally by this Ansible playbook. With Traefik being our default reverse-proxy, collecting nginx metrics is less relevant.
Prerequisite
To make use of this, you need to install Prometheus either via the playbook or externally. When using an external Prometheus, configuration adjustments are necessary — see Save metrics on an external Prometheus server.
If your setup includes Grafana, a dedicated NGINX PROXY
Grafana dashboard will be created.
Adjusting the playbook configuration
Add the following configuration to your inventory/host_vars/matrix.example.com/vars.yml
file:
matrix_prometheus_nginxlog_exporter_enabled: true
Save metrics on an external Prometheus server (optional)
Warning
Metrics and resulting graphs can contain a lot of information. NginX logs contain information like IP address, URLs, UserAgents and more. This information can reveal usage patterns and could be considered Personally Identifiable Information (PII). Think about this before enabling (anonymous) access. Please make sure you change the default Grafana password.
The playbook will automatically integrate the metrics into the Prometheus server provided with this playbook (if enabled). In such cases, the metrics endpoint is not exposed publicly — it's only available on the container network.
When using an external Prometheus server, you'll need to expose metrics publicly. See Collecting metrics to an external Prometheus server.
You can either use matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled: true
to expose just this one service, or matrix_metrics_exposure_enabled: true
to expose all services.
Whichever way you go with, this service will expose its metrics endpoint without password-protection at https://matrix.example.com/metrics/nginxlog
by default.
For password-protection, use (matrix_metrics_exposure_http_basic_auth_enabled
and matrix_metrics_exposure_http_basic_auth_users
) or (matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled
and matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users
).
Docker Image Compatibility (optional)
At the moment of writing only images for amd64
and arm64
architectures are available. The playbook currently does not support self-building a container image on other architectures. You can however use a custom-build image by setting:
matrix_prometheus_nginxlog_exporter_docker_image_arch_check_enabled: false
matrix_prometheus_nginxlog_exporter_docker_image: path/to/docker/image:tag
Extending the configuration
There are some additional things you may wish to configure about the component.
Take a look at:
roles/custom/matrix-prometheus-nginxlog-exporter/defaults/main.yml
for some variables that you can customize via yourvars.yml
file
Installing
After configuring the playbook, run it with playbook tags as below:
ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
The shortcut commands with the just
program are also available: just install-all
or just setup-all
just install-all
is useful for maintaining your setup quickly (2x-5x faster than just setup-all
) when its components remain unchanged. If you adjust your vars.yml
to remove other components, you'd need to run just setup-all
, or these components will still remain installed. Note these shortcuts run the ensure-matrix-users-created
tag too.
Troubleshooting
As with all other services, you can find the logs in systemd-journald by logging in to the server with SSH and running journalctl -fu matrix-prometheus-nginxlog-exporter
.