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
@@ -22,6 +22,12 @@ tls = true                       # ee / FakeTLS

 [server]
 port = 1080
+# Host TCP :9090 is Cockpit, so compose maps host 192.168.0.35:9092 to this
+# container port. Explicit 0.0.0.0 is required because metrics_port alone binds
+# Telemt 3.4.25 to container loopback. Only the client-02 Zabbix server may scrape.
+metrics_port = 9090
+metrics_listen = "0.0.0.0:9090"
+metrics_whitelist = ["192.168.0.34/32"]

 [censorship]
 tls_domain = "www.google.com"    # SNI presented in the Fake-TLS handshake; tunable