Configuring the agent as a proxy

The v2 agent can function as a proxy for other servers that do not have internet access. 

Due to compatibility issues this proxy method does not work with CentOS 5.

  1. Specify a server that runs sd-agent as your proxy. For this example the server is named sd-proxy. This node must be able to reach your Server Density URL.
  2. Verify SSL connectivity on sd-proxy.
    curl -iX GET | grep "200 OK"
  3. Ensure that non-local traffic is allowed on sd-proxy by adding the following line in your sd-proxy agent config.cfg 
    non_local_traffic: yes
  4. Test that the sd-proxy server can be reached from your other servers over port 17123. Ensure that the agent is started on sd-proxy and run the command below on your non-proxy hosts. This assumes local DNS records are already in place to resolve sd-proxy to the correct ip:
    curl -v http://sd-proxy:17123/status 2>&1 | grep "200 OK"
  5. Update non-proxy servers to forward to sd-proxy. Simply add the following line in your sd-proxy config.cfg and make sure the agent key is correct (Note that on the non-proxy servers you do not need to specify the sd_account parameter):
    sd_url: http://sd-proxy:17123
  6. Verify in your Server Density dashboard that metrics are being received.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Monday  —  Friday.

10am  —  6pm UK.

Dedicated Support.