technohim/docker-infrastructure
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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

Browse Source 
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.
This commit is contained in:
pipistrello
2026-07-27 09:38:11 +03:00
parent 8f95385b89
commit 229fddfc89
3 changed files with 18 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tailscale-proxy/README.md
+9
View File
@@ -39,3 +39,12 @@ configuration files must already exist on the host before deployment.
Full build record and rationale (userspace vs TUN dead-ends, SOCKS5-vs-HTTP,
monitoring) is in ops-knowledge:
`diagnostics/2026-07-23-02-tekhnohim-docker-tailscale-exit-proxy-stack.md`.
## Telemt monitoring
Telemt exports Prometheus metrics on container port `9090`, published as
`http://192.168.0.35:9092/metrics` because host port `9090` is reserved by
Cockpit. The Telemt application whitelist permits only the client-02 Zabbix
server (`192.168.0.34/32`). In Zabbix, import Telemt's upstream
`tools/zbx_telemt_template.yaml`, link it to the Docker host, and set
`{$TELEMT_URL}` to the URL above.