drop advanced defaults for datadog plugin, leave these documented upstream in the datadogunifi README

This commit is contained in:
Cody Lee 2022-01-18 09:55:32 -06:00
parent 89587ae8d2
commit 273ff7c90f
No known key found for this signature in database
GPG Key ID: 3C27FB622A28E065
1 changed files with 0 additions and 64 deletions

View File

@ -83,70 +83,6 @@
# tags to append to all data
# tags = [ "customer:abc_corp" ]
# max_bytes_per_payload is the maximum number of bytes a single payload will contain.
# The magic value 0 will set the option to the optimal size for the transport
# protocol used when creating the client: 1432 for UDP and 8192 for UDS.
# max_bytes_per_payload = 0
# max_messages_per_payload is the maximum number of metrics, events and/or service checks a single payload will contain.
# This option can be set to `1` to create an unbuffered client. Default is 0 to use the default datadog statsd
# client max messages.
# max_messages_per_payload = 0
# BufferPoolSize is the size of the pool of buffers in number of buffers.
# The magic value 0 will set the option to the optimal size for the transport
# protocol used when creating the client: 2048 for UDP and 512 for UDS.
# buffer_pool_size = 0
# buffer_flush_interval is the interval after which the current buffer will get flushed.
# Default is 0 to use the default datadog statsd setting.
# buffer_flush_interval = 0
# buffer_shard_count is the number of buffer "shards" that will be used.
# Those shards allows the use of multiple buffers at the same time to reduce
# lock contention.
# Default is 0 to use the default datadog statsd setting.
# buffer_shard_count = 0
# sender_queue_size is the size of the sender queue in number of buffers.
# The magic value 0 will set the option to the optimal size for the transport
# protocol used when creating the client: 2048 for UDP and 512 for UDS.
# Default is 0 to use the default datadog statsd setting.
# sender_queue_size = 0
# write_timeout_uds is the timeout after which a UDS packet is dropped. This is only useful when in UDS mode.
# Default is 5000 to use the default datadog statsd setting.
# write_timeout_uds = 5000
# receive_mode determines the behavior of the client when receiving to many
# metrics. The client will either drop the metrics if its buffers are
# full (ChannelMode mode) or block the caller until the metric can be
# handled (MutexMode mode). By default the client will MutexMode. This
# option should be set to ChannelMode only when use under very high
# load.
#
# MutexMode uses a mutex internally which is much faster than
# channel but causes some lock contention when used with a high number
# of threads. Mutex are sharded based on the metrics name which
# limit mutex contention when goroutines send different metrics.
#
# ChannelMode: uses channel (of ChannelModeBufferSize size) to send
# metrics and drop metrics if the channel is full. Sending metrics in
# this mode is slower that MutexMode (because of the channel), but
# will not block the application. This mode is made for application
# using many goroutines, sending the same metrics at a very high
# volume. The goal is to not slow down the application at the cost of
# dropping metrics and having a lower max throughput.
# Default 0 is mutex mode, 1 is channel mode.
# receive_mode = 0
# channel_mode_buffer_size is the size of the channel holding incoming metrics
# Default is 0 to use the default datadog statsd setting.
# channel_mode_buffer_size = 0
# aggregation_flush_interval is the interval for the aggregator to flush metrics
# Default is 0 to use the default datadog statsd setting.
# aggregation_flush_interval = 0
# Unpoller has an optional web server. To turn it on, set enable to true. If you
# wish to use SSL, provide SSL cert and key paths. This interface is currently