tailscale-proxy: expose Telemt metrics to client-02 Zabbix

Publish Telemt's container metrics port 9090 as 192.168.0.35:9092 because Cockpit already owns host port 9090. Bind the application listener to 0.0.0.0 inside the container and restrict Telemt's metrics whitelist to the client-02 Zabbix server at 192.168.0.34/32.\n\nDocument the Zabbix template macro URL and the Telemt 3.4.25 loopback-binding gotcha. The live endpoint returned HTTP 200 with 40,235 bytes from the Zabbix server; Telemt remained healthy and rebuilt its Telegram DC connections in six seconds.
2026-07-27 09:38:11 +03:00
parent 8f95385b89
commit 229fddfc89
3 changed files with 18 additions and 1 deletions
@@ -54,9 +54,11 @@ services:
      - "/mnt/containers/tailscale-proxy/telemt/telemt.toml:/app/config.toml:ro,z"
    ports:
      - "192.168.0.35:1080:1080"
+      # Host :9090 belongs to Cockpit; expose Telemt metrics on :9092 instead.
+      - "192.168.0.35:9092:9090"
    # Stays on json-file: telemt's tracing logs don't ship cleanly over the
    # syslog driver, and `docker logs ts-lan-telemt` is worth keeping for this
-    # critical service. Observe it there (or wire its Prometheus metrics later).
+    # critical service. Prometheus metrics are scraped by Zabbix on :9092.
    networks: [proxynet]

 networks: