Advanced proxy configuration includes use of configuration properties, annotating your sources with SourceTag and SourceDescription properties, and performing advanced installation management.
This document describes Wavefront proxy 4.12 configuration options. For changes since previous proxy versions, see Wavefront Proxy Versions.
Proxy Configuration Properties
The main Wavefront proxy configuration file is maintained in
<wf_config_path>/wavefront.conf). The configuration file offers many options for changing how the proxy processes your data. There are optional configuration files for rewriting metrics and parsing log data. The default values work well in many cases, but you can adjust them as needed. After changing a configuration option, restart the proxy service.
In this section, file paths use the following conventions and values:
- Linux -
- Mac -
- Windows -
C:\Program Files (x86)\Wavefront\conf
- Linux -
- Linux -
- Mac -
- Windows -
C:\Program Files (x86)\Wavefront
- Linux -
- Linux -
- Mac -
- Windows -
C:\Program Files (x86)\Wavefront\bin
- Linux -
Properties and Examples
|agentMetricsPointTags||Point tags and their values to be passed along with
||Comma-separated list of key-value pairs.
|blacklistRegex||Regex pattern (java.util.regex) that input lines must match to be filtered out. Input lines are checked against the pattern as they come in and before the prefix is prepended.||Valid regex pattern.
Ex: Filter out points that begin with qa., development., or test.:^(qa|development|test).
|buffer||Location of buffer files for saving failed transmissions for retry.||Valid path on the local file system.
|customSourceTags||Point tag keys to use as 'source' if no 'source' or 'host' field is present. Default: fqdn, hostname.||Comma-separated list of point tag keys.
Ex: fqdn, hostname
|dataBackfillCutoffHours||The cut-off point for what is considered a valid timestamp for back-dated points. We do not recommend setting this value larger than 1 year unless backfilling or migrating historic data. Default: 8760 (1 year), so all points older than 1 year are rejected.||Positive integer.
|ephemeral||Whether to automatically clean up old and orphaned proxy instances from the Wavefront Proxies page. We recommend enabling ephemeral mode if you're running the proxy in a container that may be frequently spun down and recreated. Default: false.||Boolean
|fileBeatPort||TCP port to listen on for Filebeat data. Default: 5044.||A port number.
|flushThreads||Number of threads that flush data to the server. Setting this value too high results in sending batches that are too small to the Wavefront server and wasting connections. Values between 6 and 16 are a good starting point. This setting is per listening port. Default: The number of available processors (min 4).||Positive integer.
|graphiteDelimiters||Characters that should be replaced by dots, in case they were escaped within Graphite and collectd before sending. A common delimiter is the underscore character; so if you extract a hostname field with the value
||A concatenation of delimiter characters, without any separators.|
|graphiteFormat||Indexes of fields within Graphite and collectd metric names that correspond to a hostname. For example, if your metrics have the format:
||Comma-separated list of indexes.
Ex: 4, 2, 5
|graphitePorts||TCP ports to listen on for Graphite data. Define which of the segments in your Graphite metrics map to a hostname in the graphiteFormat property. Default: 2003.||Comma-separated list of available port numbers. Can be a single port.
Ex: 2003, 2004
|hostname||A name unique across your account representing the machine that the proxy is running on. The hostname is not used to tag your metrics; rather, it's used to tag proxy metrics, such as JVM statistics, per-proxy point rates, and so on.||A string containing alphanumeric characters and periods.|
|httpConnectTimeout||HTTP connect timeout (in milliseconds). Default: 5000 (5s).||Positive integer.
|httpRequestTimeout||HTTP request timeout (in milliseconds). We do not recommend setting this value to be higher than 20000. Recommended value for most configurations is 10000 (10 seconds). Default: 10000 (10s).||Positive integer.
|httpUserAgent||Override User-Agent in request headers. Can help bypass excessively restrictive filters on the HTTP proxy. Default user agent:
|idFile||Location of the PID file for the wavefront-proxy process. Default:
||Valid path on the local file system.|
|jsonListenerPorts||TCP ports to listen on for incoming JSON-formatted metrics. Default: None.||Comma-separated list of available port numbers. Can be a single port.|
|logsIngestionConfigFile||The file containing instructions for parsing log data into metrics. See Log Data Metrics Integration.
||Valid path on the local file system.||4.1|
|opentsdbPorts||TCP ports to listen on for incoming OpenTSDB-formatted data. Default: None.||Comma-separated list of available port numbers. Can be a single port.
|picklePorts||TCP ports to listen on for incoming data in Graphite pickle format (from carbon-relay). Default: None.||Comma-separated list of available port numbers. Can be a single port.
|prefix||String to prepend before every metric name. For example, if you set prefix to 'production', a metric that is sent to the proxy as
||A lowercase alphanumeric string, with periods separating segments. You do not need to include a trailing period.
|preprocessorConfigFile||Path to the optional preprocessor config file containing preprocessor rules for filtering and rewriting metrics. Default: None.||Valid path on the local file system.
|proxyHost||HTTP proxy host to be used in configurations when direct HTTP connections to Wavefront servers are not possible. Must be used with proxyPort.||A string.
|proxyPassword||When used with proxyUser, sets credentials to use with the HTTP proxy if the proxy requires authentication.||A string.
|proxyPort||HTTP proxy port to be used in configurations when direct HTTP connections to Wavefront servers are not possible. Must be used with proxyHost.||A port number.
|proxyUser||When used with proxyPassword, sets credentials to use with the HTTP proxy if the proxy requires authentication.||A string.
|pushBlockedSamples||Number of blocked points to print to the log immediately following each summary line (every 10 flushes). If 0, print none. If you see a non-zero number of blocked points in the summary lines and want to debug what that data is, set this property to 5. Default: 0.||0 or a positive integer.
|pushFlushInterval||Milliseconds to wait between each flush to Wavefront. Default: 1000.||An integer equal to or greater than 1000.
|pushFlushMaxPoints||Maximum number of points to send to Wavefront during each flush. Default: 40,000.||Positive integer.
|pushListenerPorts||TCP ports to listen on for incoming data. Default: 2878.||Comma-separated list of available port numbers. Can be a single port.
|pushLogLevel||Frequency to print status information on the data flow to the log. SUMMARY prints a line every 60 flushes, while DETAILED prints a line on each flush.||None, SUMMARY, or DETAILED
|pushMemoryBufferLimit||Maximum number of points that can stay in memory buffers before spooling to disk. Setting this value lower than default reduces memory usage but forces the proxy to queue points by spooling to disk more frequently, if you have points arriving at the proxy in short bursts. Default: 16 * pushFlushMaxPoints. Minimum: pushFlushMaxPoints.||Positive integer.
|pushRateLimit||Maximum number of points per second to send to Wavefront. Default: unlimited.||Positive integer.
|pushValidationLevel||Level of validation to perform on incoming data before sending the data to Wavefront. If NO_VALIDATION, all data is sent forward. If NUMERIC_ONLY, data is checked to make sure that it is numerical and dropped locally if it is not.||NUMERIC_ONLY or NO_VALIDATION
|rawLogsPort||TCP port to listen on for log data. Default: 5045.||A port number.
|retryBackoffBaseSeconds||For exponential back-off when retry threads are throttled, the base (a in a^b) in seconds. Default: 2.0.||Positive number, integer or decimal.
|retryThreads||Number of threads retrying failed transmissions. If no value is specified, defaults to the number of processor cores available to the host or 4, whichever is greater. Every retry thread uses a separate buffer file (capped at 2GB) to persist queued data points, so the number of threads controls the maximum amount of space that the proxy can use to buffer points locally.||Positive integer.
|server||The API URL of the Wavefront server in the format https://<wf_instance>.wavefront.com/api/.|
|soLingerTime||Enable SO_LINGER with the specified linger time in seconds. Set this value to 0 when running in a high-availability configuration under a load balancer. Default: 0 (disabled).||
0 or a positive integer.Ex: 0
|splitPushWhenRateLimited||Whether to split the push batch size when the push is rejected by Wavefront due to rate limit. Default: false.||true or false
|whitelistRegex||Regex pattern (java.util.regex). Input lines are checked against the pattern as they come in and before the prefix is prepended. Only input lines that match are accepted.||Valid regex pattern.
Allows points that begin with production. and stage.
|writeHttpJsonListenerPorts||Ports to listen on for incoming data from the collectd write_http plugin. Default: None.||Comma-separated list of available port numbers. Can be a single port.
Sending Source Tags and Source Descriptions Through the Wavefront Proxy
In environments with large datasets, you might want to have the proxy client, e.g. Telegraf, add source tags and source descriptions to the data before the data reaches Wavefront. You can use the SourceTag and SourceDescription properties to do that, when the proxy is running. You use a client-specific API or CLI on the source data to insert SourceTag and SourceDescription properties. The proxy will then pick up that information.
Starting with proxy version 4.24, this feature is available on the same listening port as regular metrics (
pushListenerPort setting, 2878 by default).
|SourceTag||Save or delete a source tag. For example, you use this property to inject a source tag into a database on a host. Use SourceTag with
|SourceDescription||Save or delete a description on the specified source. You can use this property to add a description or delete an existing description. Use SourceDescriptor with
If the Wavefront proxy is unable to post received data to the Wavefront servers, it buffers the data to disk across a number of buffer files, and then tries to resend the points once the connection to the Wavefront servers is available again. If this buffering occurs, you’ll see lines like this in
2013-11-18 18:02:35,061 WARN [com.wavefront.daemon.QueuedSshDaemonService] current retry queue sizes: [1/0/0/0]
By default, there are 4 threads (and 4 buffer files) waiting to retry points once the connections are up; this line shows how many blocks of points have been stored by each thread (in this case, the first thread has 1 block of queued points, while the second, third, and fourth threads all have 0 blocks). These lines are only printed when there are points in the queue; you’ll never see a line with all 0’s in the queue sizes. Once the connection to the Wavefront servers has been established, and all the threads have sent the past data to us, you’ll see a single line like this in
2013-11-18 18:59:46,665 WARN [com.wavefront.daemon.QueuedSshDaemonService] retry queue has been cleared
The Wavefront proxy supports two log files: proxy log and blocked point log. To keep the log file sizes reasonable and avoid filling up the disk with logs, both log files are automatically rotated and purged periodically. You configure the log file locations and rotation rules in
<wavefront_config_path>/log4j2.xml. For details on log4j2 configuration, see Log4j Configuration.
By default, proxy log entries are logged to
<wavefront_log_path>/wavefront.log. The log file is rolled over every day and when its size reaches 100MB. When there are 31 log files, older files are deleted.
Blocked Point Log
You can log raw blocked points in a separate log from the proxy log. Logging of blocked points is disabled by default. To enable logging block points, edit the log4j2 configuration file and uncomment the blocked points file appender:
<!-- <AppenderRef ref="BlockedPointsFile"/> -->
By default, blocked point entries are logged to
<wavefront_log_path>/wavefront-blocked-points.log and the block point log file is rolled over every day and when its size reaches 100MB. When there are 31 log files, older files are deleted.
Configuring a Proxy in a Container
You can use the in-product Docker with cAdvisor or Kubernetes integration if you want to set up a proxy in a container. You can then customize that proxy.
Proxy Versions for Containers
For containers, the proxy image version is determined by the
image property in the configuration file. You can set this to
image: wavefronthq/proxy:latest, or specify a proxy version explicitly.
The proxies are not stateful. Your configuration is managed in your
yaml file. It’s safe to use
proxy:latest – we ensure that proxies are backward compatible.
Customizing Proxy Settings for Docker
When you run a Wavefront proxy inside a Docker container, you can tweak proxy configuration settings that are properties in the
wavefront.conf file directly from the Docker
run command. You use the WAVEFRONT_PROXY_ARGS environment variable and pass in the property name as a long form argument, preceded by
For example, add
e WAVEFRONT_PROXY_ARGS="--pushRateLimit 1000" to your docker
run command to specify a rate limit of 1000 pps for the proxy.
See the Wavefront Proxy configuration file for a full list.
Installing Proxies on Multiple Linux Hosts
Ansible is an open-source automation engine that automates software provisioning, configuration and management, and application deployment. The Wavefront Ansible role installs and configures the Wavefront proxy, which allows you to automate Wavefront proxy installation on multiple Linux hosts.
Note: In most cases, you install only one or two proxies in your environment. You don’t need a proxy for each host you collect data from. See Proxy Deployment Options.
For details, see the Setup tab in the Ansible built-in integration.