c77f2b8a64
* if variable to bind an exporter container to a host port is set, have matrix-domain.conf (nginx) support this * manipulate some variables to account for just port numbers or 0.0.0.0 IPs * Make sure to use the right variable in the init.yml files * Update roles/matrix-prometheus-node-exporter/tasks/init.yml Co-authored-by: Slavi Pantaleev <slavi@devture.com> * Update roles/matrix-prometheus-postgres-exporter/tasks/init.yml Co-authored-by: Slavi Pantaleev <slavi@devture.com> * remove extraneous variables and whitespace Co-authored-by: Luca Bilke <luca@gmail.com> Co-authored-by: Slavi Pantaleev <slavi@devture.com>
63 lines
4.3 KiB
YAML
63 lines
4.3 KiB
YAML
---
|
|
# matrix-prometheus-node-exporter is an Prometheus exporter for machine metrics
|
|
# See: https://prometheus.io/docs/guides/node-exporter/
|
|
# Project source code URL: https://github.com/prometheus/node_exporter
|
|
|
|
matrix_prometheus_node_exporter_enabled: false
|
|
|
|
matrix_prometheus_node_exporter_version: v1.3.1
|
|
matrix_prometheus_node_exporter_docker_image: "{{ matrix_container_global_registry_prefix }}prom/node-exporter:{{ matrix_prometheus_node_exporter_version }}"
|
|
matrix_prometheus_node_exporter_docker_image_force_pull: "{{ matrix_prometheus_node_exporter_docker_image.endswith(':latest') }}"
|
|
|
|
# A list of extra arguments to pass to the container
|
|
matrix_prometheus_node_exporter_container_extra_arguments: []
|
|
|
|
# A list of extra arguments to pass to the node_exporter process
|
|
#
|
|
# Example:
|
|
# matrix_prometheus_node_exporter_process_extra_arguments:
|
|
# - "--collector.systemd"
|
|
# - "--collector.logind"
|
|
#
|
|
# Note: the above is just an example. Various collectors may require various tweaks to be able to run.
|
|
# Running the systemd collector requires the following `matrix_prometheus_node_exporter_container_extra_arguments`:
|
|
# - the socket to be mounted as well (`--mount type=bind,src=/var/run/dbus/system_bus_socket,dst=/var/run/dbus/system_bus_socket,ro,bind-propagation=rslave`)
|
|
# - (on AppArmor-based distros) disabling AppArmor protection (`--security-opt apparmor=unconfined`)
|
|
matrix_prometheus_node_exporter_process_extra_arguments: []
|
|
|
|
# List of systemd services that matrix-prometheus.service depends on
|
|
matrix_prometheus_node_exporter_systemd_required_services_list: ['docker.service']
|
|
|
|
# List of systemd services that matrix-prometheus.service wants
|
|
matrix_prometheus_node_exporter_systemd_wanted_services_list: []
|
|
|
|
# Controls whether node-exporter metrics should be proxied (exposed) on `matrix.DOMAIN/metrics/node-exporter`.
|
|
# This will only work take effect if `matrix_nginx_proxy_proxy_matrix_metrics_enabled: true`.
|
|
# See the `matrix-nginx-proxy` role for details about enabling `matrix_nginx_proxy_proxy_matrix_metrics_enabled`.
|
|
matrix_prometheus_node_exporter_metrics_proxying_enabled: false
|
|
|
|
# Controls whether the matrix-prometheus container exposes its HTTP port (tcp/9100 in the container).
|
|
#
|
|
# Takes an "<ip>:<port>" value (e.g. "127.0.0.1:9100"), just a port number or empty string to not expose.
|
|
#
|
|
# You likely don't need to do this. See `matrix_prometheus_node_exporter_metrics_proxying_enabled`.
|
|
#
|
|
# Official recommendations are to run this container with `--net=host`,
|
|
# but we don't do that, since it:
|
|
# - likely exposes the metrics web server way too publicly (before applying https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1008)
|
|
# - or listens on a loopback interface only (--net=host and 127.0.0.1:9100), which is not reachable from another container (like `matrix-prometheus`)
|
|
#
|
|
# Using `--net=host` and binding to Docker's `matrix` bridge network may be a solution to both,
|
|
# but that's trickier to accomplish and won't necessarily work (hasn't been tested).
|
|
#
|
|
# Not using `--net=host` means that our network statistic reports are likely broken (inaccurate),
|
|
# because node-exporter can't see all interfaces, etc.
|
|
# For now, we'll live with that, until someone develops a better solution.
|
|
matrix_prometheus_node_exporter_container_http_host_bind_port: ''
|
|
|
|
# If you are supplying your own NGINX proxy but want to use the provided exporters you will have to supply an "<ip>:<port>" value for the containers to bind to on your host.
|
|
# If matrix_prometheus_node_exporter_container_http_host_bind_port is set to just a port number, this will default to "127.0.0.1:<port>"
|
|
# If matrix_prometheus_node_exporter_container_http_host_bind_port is set to an IP that is not 0.0.0.0 and a port, that "<ip>:<port>" value will be used
|
|
# Otherwise this value will be empty and you will have to manually configure your NGINX config file. (If you are using the config files generated by this playbook, you will have to edit matrix-domain.conf)
|
|
matrix_prometheus_node_exporter_matrix_nginx_proxy_not_enabled_proxy_pass_host: "{{ '127.0.0.1' + matrix_prometheus_node_exporter_container_http_host_bind_port_number_raw if not ':' in matrix_prometheus_node_exporter_container_http_host_bind_port else (matrix_prometheus_node_exporter_container_http_host_bind_port if matrix_prometheus_node_exporter_container_http_host_bind_port.split(':')[0] != '0.0.0.0' else '') }}"
|