Remote Server Monitoring over VPN: A Docker Approach (Part 2)
Recap: Where We Left Off In Part 1 of this series, we established our secure foundation: an encrypted L3 bridge using AmneziaWG and Docker's Network Namespace sharing ( network_mode ). We already have our first agent, node-exporter , silently listening inside the tunnel on the remote node at 10.10.0.2:9100 . The traffic is encrypted, the ports are invisible to the public internet, and the whole thing is defined as code. But metrics sitting on a remote node are useless if nothing collects and vis
Comment
Sign in to join the discussion.
Loading comments…