This article applies to:
• Data Ingestion
• Feature Category: VMware Aria Operations for Applications Proxy
• Product edition: 5.x or later
Overview:
Currently there are two methodologies to deploying the VMware Aria Operations for Applications Proxy:
To utilize wavefront.conf configuration file for a VMware Aria Operations for Applications Proxy running as a container, please use the details below:
Prior to utilizing a wavefront.conf configuration file on a VMware Aria Operations for Applications Proxy running as a container, a wavefront.conf file needs to be configured and stored where the container host can access.
Utilize the below docker run example replacing <myinstance> with your VMware Aria Operations for Applications Cluster name, <YOUR-API-TOKEN> with the API token the VMware Aria Operations for Applications Proxy will utilize, and </path/to/file> with the path to where the wavefront.conf is available on the container's host.
This example command will load the volume file wavefront.conf on the start of the VMware Aria Operations for Applications Proxy service startup.
docker run \
-e WAVEFRONT_URL=https://<myinstance>.wavefront.com/api \
-e WAVEFRONT_TOKEN=<YOUR-API-TOKEN> \
-e WAVEFRONT_PROXY_ARGS='-f /etc/wavefront/wavefront-proxy/wavefront.conf' \
-v </path/to/file>/wavefront.conf:/etc/wavefront/wavefront-proxy/wavefront.conf:ro \
-p 2878:2878 \
wavefronthq/proxy:latest