From edc31a9391893823aca4c5822fa527554fca768a Mon Sep 17 00:00:00 2001 From: Sean Kilgore Date: Tue, 24 May 2016 12:55:23 -0700 Subject: [PATCH] docs: clarify address specification for telemetry Earlier on this page, under `addresses`, we say "For TCP addresses, these should simply be an IP address without the port. For example: 10.0.0.1, not 10.0.0.1:8500." Since we expect the port to be included for `_address` for telemetry, call it out specifically. --- website/source/docs/agent/options.html.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/docs/agent/options.html.markdown b/website/source/docs/agent/options.html.markdown index b2dcc778a0..e5165a9fce 100644 --- a/website/source/docs/agent/options.html.markdown +++ b/website/source/docs/agent/options.html.markdown @@ -656,12 +656,12 @@ Consul will not enable TLS for the HTTP API unless the `https` port has been ass sends its runtime telemetry, and contains the following keys: * `statsd_address` This provides the - address of a statsd instance. If provided, Consul will send various telemetry information to that instance for + address of a statsd instance in the format `host:port`. If provided, Consul will send various telemetry information to that instance for aggregation. This can be used to capture runtime information. This sends UDP packets only and can be used with statsd or statsite. * `statsite_address` This provides - the address of a statsite instance. If provided, Consul will stream various telemetry information to that instance + the address of a statsite instance in the format `host:port`. If provided, Consul will stream various telemetry information to that instance for aggregation. This can be used to capture runtime information. This streams via TCP and can only be used with statsite.