Do not override matrix_prometheus_node_exporter_container_http_host_bind_port when matrix-nginx-proxy disabled
Not sure why this had been done in the first place. It doesn't make any sense. There's no relation between matrix-nginx-proxy and prometheus-node-exporter.
This commit is contained in:
parent
398b9f5d66
commit
8da8979a24
@ -1675,11 +1675,6 @@ matrix_synapse_admin_container_self_build: "{{ matrix_architecture != 'amd64' }}
|
|||||||
|
|
||||||
matrix_prometheus_node_exporter_enabled: false
|
matrix_prometheus_node_exporter_enabled: false
|
||||||
|
|
||||||
# Normally, matrix-nginx-proxy is enabled and nginx can reach Prometheus Node Exporter over the container network.
|
|
||||||
# If matrix-nginx-proxy is not enabled, or you otherwise have a need for it, you can expose
|
|
||||||
# Prometheus' HTTP port to the local host.
|
|
||||||
matrix_prometheus_node_exporter_container_http_host_bind_port: "{{ '' if matrix_nginx_proxy_enabled else '127.0.0.1:9200' }}"
|
|
||||||
|
|
||||||
######################################################################
|
######################################################################
|
||||||
#
|
#
|
||||||
# /matrix-prometheus-node-exporter
|
# /matrix-prometheus-node-exporter
|
||||||
|
Loading…
Reference in New Issue
Block a user