Remove dead metrics support from the mautrix-bluesky bridge

Bridges based on bridgev2 no longer expose a metrics endpoint, 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:52:24 +03:00
parent 034ccf15de
commit 199fa3c432
4 changed files with 12 additions and 67 deletions
@@ -71,17 +71,6 @@ matrix_bridge_mautrix_bluesky_container_labels_traefik_docker_network: "{{ matri
matrix_bridge_mautrix_bluesky_container_labels_traefik_entrypoints: web-secure
matrix_bridge_mautrix_bluesky_container_labels_traefik_tls_certResolver: default # noqa var-naming
# Controls whether labels will be added that expose mautrix-instagram's metrics
matrix_bridge_mautrix_bluesky_container_labels_metrics_enabled: "{{ matrix_bridge_mautrix_bluesky_metrics_enabled and matrix_bridge_mautrix_bluesky_metrics_proxying_enabled }}"
matrix_bridge_mautrix_bluesky_container_labels_metrics_traefik_rule: "Host(`{{ matrix_bridge_mautrix_bluesky_metrics_proxying_hostname }}`) && PathPrefix(`{{ matrix_bridge_mautrix_bluesky_metrics_proxying_path_prefix }}`)"
matrix_bridge_mautrix_bluesky_container_labels_metrics_traefik_priority: 0
matrix_bridge_mautrix_bluesky_container_labels_metrics_traefik_entrypoints: "{{ matrix_bridge_mautrix_bluesky_container_labels_traefik_entrypoints }}"
matrix_bridge_mautrix_bluesky_container_labels_metrics_traefik_tls: "{{ matrix_bridge_mautrix_bluesky_container_labels_metrics_traefik_entrypoints != 'web' }}"
matrix_bridge_mautrix_bluesky_container_labels_metrics_traefik_tls_certResolver: "{{ matrix_bridge_mautrix_bluesky_container_labels_traefik_tls_certResolver }}" # noqa var-naming
matrix_bridge_mautrix_bluesky_container_labels_metrics_middleware_basic_auth_enabled: false
# See: https://doc.traefik.io/traefik/middlewares/http/basicauth/#users
matrix_bridge_mautrix_bluesky_container_labels_metrics_middleware_basic_auth_users: ''
# Controls whether labels will be added that expose mautrix-bluesky's HTTP API
# (used by tools like mautrix-manager for bridge login) at `https://<hostname><path_prefix>`.
matrix_bridge_mautrix_bluesky_container_labels_exposure_enabled: "{{ matrix_bridge_mautrix_bluesky_exposure_enabled }}"
@@ -161,16 +150,6 @@ matrix_bridge_mautrix_bluesky_provisioning_shared_secret: disable
# Valid values: fatal, error, warn, info, debug, trace
matrix_bridge_mautrix_bluesky_logging_level: 'warn'
# 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_bluesky_metrics_proxying_enabled`.
matrix_bridge_mautrix_bluesky_metrics_enabled: false
# Controls whether metrics should be exposed on a public URL.
matrix_bridge_mautrix_bluesky_metrics_proxying_enabled: false
matrix_bridge_mautrix_bluesky_metrics_proxying_hostname: ''
matrix_bridge_mautrix_bluesky_metrics_proxying_path_prefix: ''
# Controls whether mautrix-bluesky's HTTP API is exposed publicly (used by tools like mautrix-manager for bridge login).
matrix_bridge_mautrix_bluesky_exposure_enabled: false
matrix_bridge_mautrix_bluesky_exposure_hostname: ''