This article applies to:
• Data Ingestion
• Feature Category: Tanzu Observability (Wavefront) Proxy
• Product edition: 5.x or later
Currently there are two methodologies to deploying the Tanzu Observability Proxy:
- When the Tanzu Observability Proxy is ran as a service, the configuration of the Wavefront Proxy is performed via the wavefront.conf configuration file.
- When the Tanzu Observability Proxy is ran as a container via the wavefronthq/proxy image, the configuration of the Wavefront Proxy is performed via WAVEFRONT_PROXY_ARGS.
Configure a Wavefront Proxy Container to Use wavefront.conf:
To utilize wavefront.conf configuration file for a Tanzu Observability Proxy running as a container, please use the details below:
Prior to utilizing a wavefront.conf configuration file on a Tanzu ObservabilityProxy running as a container, a wavefront.conf file needs to be configured and stored where the container host can access.
- Copy wavefront.conf from an existing proxy to use as a template or save wavefront.conf.default to wavefront.conf.
- Configure the wavefront.conf file as desired.
- Environmental variables WAVEFRONT_URL and WAVEFRONT_TOKEN are still required to be defined outside of wavefront.conf for the container to start.
Utilize the below docker run example replacing <myinstance> with your Tanzu Observability Cluster name, <YOUR-API-TOKEN> with the API token the Tanzu Observability 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 Wavefront 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 \