spantaleev/matrix-docker-ansible-deploy
1
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2026-08-06 16:03:06 +10:00
Code Issues Packages Projects Releases Wiki Activity

Remove dead metrics support from the mautrix-telegram bridge

Browse Source 
The bridge lost its metrics endpoint when it was rewritten on top of
bridgev2, so the playbook was publishing a Traefik route which could
only ever yield an HTTP 502.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5487
This commit is contained in:
Slavi Pantaleev
2026-08-04 16:57:41 +03:00
parent 2daa19ea91
commit 398a5ab95e
4 changed files with 12 additions and 67 deletions
Download Patch File Download Diff File Expand all files Collapse all files
roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml
-21
View File
@@ -77,17 +77,6 @@ matrix_bridge_mautrix_telegram_container_labels_traefik_docker_network: "{{ matr
matrix_bridge_mautrix_telegram_container_labels_traefik_entrypoints: web-secure
matrix_bridge_mautrix_telegram_container_labels_traefik_tls_certResolver: default # noqa var-naming
# Controls whether labels will be added that expose mautrix-telegram's metrics
matrix_bridge_mautrix_telegram_container_labels_metrics_enabled: "{{ matrix_bridge_mautrix_telegram_metrics_enabled and matrix_bridge_mautrix_telegram_metrics_proxying_enabled }}"
matrix_bridge_mautrix_telegram_container_labels_metrics_traefik_rule: "Host(`{{ matrix_bridge_mautrix_telegram_metrics_proxying_hostname }}`) && PathPrefix(`{{ matrix_bridge_mautrix_telegram_metrics_proxying_path_prefix }}`)"
matrix_bridge_mautrix_telegram_container_labels_metrics_traefik_priority: 0
matrix_bridge_mautrix_telegram_container_labels_metrics_traefik_entrypoints: "{{ matrix_bridge_mautrix_telegram_container_labels_traefik_entrypoints }}"
matrix_bridge_mautrix_telegram_container_labels_metrics_traefik_tls: "{{ matrix_bridge_mautrix_telegram_container_labels_metrics_traefik_entrypoints != 'web' }}"
matrix_bridge_mautrix_telegram_container_labels_metrics_traefik_tls_certResolver: "{{ matrix_bridge_mautrix_telegram_container_labels_traefik_tls_certResolver }}" # noqa var-naming
matrix_bridge_mautrix_telegram_container_labels_metrics_middleware_basic_auth_enabled: false
# See: https://doc.traefik.io/traefik/middlewares/http/basicauth/#users
matrix_bridge_mautrix_telegram_container_labels_metrics_middleware_basic_auth_users: ''
# Controls whether labels will be added that expose mautrix-telegram's HTTP API
# (used by tools like mautrix-manager for bridge login) at `https://<hostname><path_prefix>`.
matrix_bridge_mautrix_telegram_container_labels_exposure_enabled: "{{ matrix_bridge_mautrix_telegram_exposure_enabled }}"
@@ -131,16 +120,6 @@ matrix_bridge_mautrix_telegram_logging_level: 'warn'
# If false, created portal rooms will never be federated.
matrix_bridge_mautrix_telegram_federate_rooms: true
# Whether or not metrics endpoint should be enabled.
# Enabling them is usually enough for a local (in-container) Prometheus to consume them.
# If metrics need to be consumed by another (external) Prometheus server, consider exposing them via `matrix_bridge_mautrix_telegram_metrics_proxying_enabled`.
matrix_bridge_mautrix_telegram_metrics_enabled: false
# Controls whether metrics should be proxied (exposed) on a public URL
matrix_bridge_mautrix_telegram_metrics_proxying_enabled: false
matrix_bridge_mautrix_telegram_metrics_proxying_hostname: ''
matrix_bridge_mautrix_telegram_metrics_proxying_path_prefix: ''
# Controls whether mautrix-telegram's HTTP API is exposed publicly (used by tools like mautrix-manager for bridge login).
matrix_bridge_mautrix_telegram_exposure_enabled: false
matrix_bridge_mautrix_telegram_exposure_hostname: ''