Adding upstream version 1.34.4.
Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
parent
e393c3af3f
commit
4978089aab
4963 changed files with 677545 additions and 0 deletions
108
plugins/outputs/wavefront/sample.conf
Normal file
108
plugins/outputs/wavefront/sample.conf
Normal file
|
@ -0,0 +1,108 @@
|
|||
[[outputs.wavefront]]
|
||||
## URL for Wavefront API or Wavefront proxy instance
|
||||
## Direct Ingestion via Wavefront API requires authentication. See below.
|
||||
url = "https://metrics.wavefront.com"
|
||||
|
||||
## Maximum number of metrics to send per HTTP request. This value should be
|
||||
## higher than the `metric_batch_size`. Values higher than 40,000 are not
|
||||
## recommended.
|
||||
# http_maximum_batch_size = 10000
|
||||
|
||||
## Prefix for metrics keys
|
||||
# prefix = "my.specific.prefix."
|
||||
|
||||
## Use "value" for name of simple fields
|
||||
# simple_fields = false
|
||||
|
||||
## character to use between metric and field name
|
||||
# metric_separator = "."
|
||||
|
||||
## Convert metric name paths to use metricSeparator character
|
||||
## When true will convert all _ (underscore) characters in final metric name.
|
||||
# convert_paths = true
|
||||
|
||||
## Use Strict rules to sanitize metric and tag names from invalid characters
|
||||
## When enabled forward slash (/) and comma (,) will be accepted
|
||||
# use_strict = false
|
||||
|
||||
## Use Regex to sanitize metric and tag names from invalid characters
|
||||
## Regex is more thorough, but significantly slower.
|
||||
# use_regex = false
|
||||
|
||||
## Tags to use as the source name for Wavefront ("host" if none is found)
|
||||
# source_override = ["hostname", "address", "agent_host", "node_host"]
|
||||
|
||||
## Convert boolean values to numeric values, with false -> 0.0 and true -> 1.0
|
||||
# convert_bool = true
|
||||
|
||||
## Truncate metric tags to a total of 254 characters for the tag name value
|
||||
## Wavefront will reject any data point exceeding this limit if not truncated
|
||||
## Defaults to 'false' to provide backwards compatibility.
|
||||
# truncate_tags = false
|
||||
|
||||
## Flush the internal buffers after each batch. This effectively bypasses the
|
||||
## background sending of metrics normally done by the Wavefront SDK. This can
|
||||
## be used if you are experiencing buffer overruns. The sending of metrics
|
||||
## will block for a longer time, but this will be handled gracefully by
|
||||
## internal buffering in Telegraf.
|
||||
# immediate_flush = true
|
||||
|
||||
## Send internal metrics (starting with `~sdk.go`) for valid, invalid, and
|
||||
## dropped metrics
|
||||
# send_internal_metrics = true
|
||||
|
||||
## Optional TLS Config
|
||||
## Set to true/false to enforce TLS being enabled/disabled. If not set,
|
||||
## enable TLS only if any of the other options are specified.
|
||||
# tls_enable =
|
||||
## Trusted root certificates for server
|
||||
# tls_ca = "/path/to/cafile"
|
||||
## Used for TLS client certificate authentication
|
||||
# tls_cert = "/path/to/certfile"
|
||||
## Used for TLS client certificate authentication
|
||||
# tls_key = "/path/to/keyfile"
|
||||
## Send the specified TLS server name via SNI
|
||||
# tls_server_name = "kubernetes.example.com"
|
||||
## Use TLS but skip chain & host verification
|
||||
# insecure_skip_verify = false
|
||||
|
||||
## HTTP Timeout
|
||||
# timeout="10s"
|
||||
|
||||
## MaxIdleConns controls the maximum number of idle (keep-alive) connections
|
||||
## across all hosts. Zero means unlimited.
|
||||
# max_idle_conn = 0
|
||||
|
||||
## MaxIdleConnsPerHost, if non-zero, controls the maximum idle (keep-alive)
|
||||
## connections to keep per-host. If zero, DefaultMaxIdleConnsPerHost is used.
|
||||
# max_idle_conn_per_host = 2
|
||||
|
||||
## Idle (keep-alive) connection timeout
|
||||
# idle_conn_timeout = 0
|
||||
|
||||
## Authentication for Direct Ingestion.
|
||||
## Direct Ingestion requires one of: `token`,`auth_csp_api_token`, or
|
||||
## `auth_csp_client_credentials` (see https://docs.wavefront.com/csp_getting_started.html)
|
||||
## to learn more about using CSP credentials with Wavefront.
|
||||
## Not required if using a Wavefront proxy.
|
||||
|
||||
## Wavefront API Token Authentication, ignored if using a Wavefront proxy
|
||||
## 1. Click the gear icon at the top right in the Wavefront UI.
|
||||
## 2. Click your account name (usually your email)
|
||||
## 3. Click *API access*.
|
||||
# token = "YOUR_TOKEN"
|
||||
|
||||
## Base URL used for authentication, ignored if using a Wavefront proxy or a
|
||||
## Wavefront API token.
|
||||
# auth_csp_base_url=https://console.cloud.vmware.com
|
||||
|
||||
## CSP API Token Authentication, ignored if using a Wavefront proxy
|
||||
# auth_csp_api_token=CSP_API_TOKEN_HERE
|
||||
|
||||
## CSP Client Credentials Authentication Information, ignored if using a
|
||||
## Wavefront proxy.
|
||||
## See also: https://docs.wavefront.com/csp_getting_started.html#whats-a-server-to-server-app
|
||||
# [outputs.wavefront.auth_csp_client_credentials]
|
||||
# app_id=CSP_APP_ID_HERE
|
||||
# app_secret=CSP_APP_SECRET_HERE
|
||||
# org_id=CSP_ORG_ID_HERE
|
Loading…
Add table
Add a link
Reference in a new issue