Set Up a Pepperdata Proxy (RPM/DEB)

If your cluster hosts must be “air gapped” from the internet or otherwise isolated, you can use a proxy server on your network to enable Pepperdata functionality. Pepperdata is fully integrated with the standard https_proxy environment variable, which you can configure in the Pepperdata configuration file, /etc/pepperdata/pepperdata-config.sh.

Procedure

1. Configure the environment variable for the proxy host and port, https_proxy.

   1. On any host in the cluster, open the Pepperdata configuration file, /etc/pepperdata/pepperdata-config.sh, for editing.

   2. Uncomment and update the environment variable for the proxy host and port, in the following format. Be sure to replace the my_proxy_url and my_proxy_port placeholders with your actual proxy server name and port number.

      export https_proxy=my_proxy_url:my_proxy_port

   3. Save your changes and close the file.

2. On every host in the cluster, restart the PepCollector and PepAgent services.

   1. Restart the Pepperdata Collector.

      You can use either the service (if provided by your OS) or systemctl command:

      • sudo service pepcollectd restart
      • sudo systemctl restart pepcollectd

   2. Restart the PepAgent.

      You can use either the service (if provided by your OS) or systemctl command:

      • sudo service pepagentd restart
      • sudo systemctl restart pepagentd

3. (Optional) Verify that hosts can connect to the Pepperdata dashboard through the proxy server as it’s configured.

   1. Log in to the host that you want to test.

   2. Source the Pepperdata configuration.

      source /etc/pepperdata/pepperdata-config.sh

   3. Use cURL to connect to the Pepperdata dashboard.

      curl --tlsv1.2 -v https://upload-main.pepperdata.com

   A successful connection confirms that the proxy server is correctly configured.