Skip to content

Configuring DogStatsD on Agent Data Plane

The DogStatsD implementation on ADP has been redesigned in Rust for better resource guarantees and efficiency. Because the architecture is different from the original implementation, certain configuration values may behave differently, be planned but not yet implemented, or not apply at all. This page documents those nuances.

ADP is designed to be transparent: customers configure DogStatsD the same way they always have. The sections below call out the cases where that is either not yet true, or not quite possible.

If you find an error on this page, please open an issue.

Unsupported Settings

Being Worked On

The following settings are not yet supported in ADP but are planned with GitHub issue links for tracking.

Config KeyDescriptionIssue
dogstatsd_capture_depthTraffic capture channel depth#1381
dogstatsd_capture_pathTraffic capture file location#1381
dogstatsd_pipe_nameWindows named pipe path#1466
dogstatsd_windows_pipe_security_descriptorWindows named pipe ACL descriptor#1466
forwarder_http_protocolHTTP version (auto/http1)#1361
forwarder_outdated_file_in_daysRetry file retention (days)#1360
serializer_experimental_use_v3_api.*V3 metrics API migration flags#1468
sslkeylogfileTLS key log file path#1372
tls_handshake_timeoutHTTP TLS handshake timeout#178

Not Planned

The following settings exist in the core agent but are not planned for ADP, typically because ADP's architecture is fundamentally different or the feature is platform-specific.

Config KeyDescriptionReason
config_idFleet Automation config ID tagCore Agent uses this only on Agent HA telemetry metrics
dogstatsd_host_socket_pathHost UDS socket dir for DSDNot read by DSD server; admission controller only
dogstatsd_mem_based_rate_limiter.*Memory-based rate limiterGo GC–specific; ADP uses memory_limit (see below)
dogstatsd_no_aggregation_pipeline_batch_sizeNo-aggregation pipeline batch sizeFixed in ADP topology
dogstatsd_packet_buffer_flush_timeoutPacket buffer flush timeoutADP decodes inline
dogstatsd_packet_buffer_sizeDatagrams per packet bufferADP decodes inline
dogstatsd_pipeline_autoadjustAuto-adjust pipeline workersADP uses async tasks
dogstatsd_pipeline_countParallel processing pipelinesADP uses async tasks
dogstatsd_queue_sizePacket channel buffer sizeADP uses async tasks
dogstatsd_telemetry_enabled_listener_idPer-listener telemetry taggingNot feasible to thread through
dogstatsd_workers_countNumber of DSD processing workersADP uses async tasks
enable_json_stream_shared_compressor_buffersShared compressor buffer poolRust request builders own fixed-capacity buffers
entity_idAgent pod entity IDADP internal DogStatsD telemetry uses OpenMetrics
heroku_dynoHeroku dyno telemetry modeCore Agent-owned Heroku Agent heartbeat behavior
use_dogstatsdMaster DogStatsD enable toggleCore Agent evaluates and sets data_plane.dogstatsd.enabled

Memory-based rate limiter (dogstatsd_mem_based_rate_limiter.*)

The Core Agent exposes configuration under this prefix to apply backpressure when the Go process approaches its memory limit. They work by manipulating Go's garbage collector (debug.SetGCPercent, debug.FreeOSMemory), allocating a large heap ballast to adjust GC heuristics, and blocking goroutines to slow packet ingestion. None of these mechanisms have an equivalent in Rust, and ADP does not use a Go runtime.

ADP takes a different approach to the same problem using explicit static memory accounting and a process-level RSS limit. All 11 dogstatsd_mem_based_rate_limiter.* keys are ignored. See Memory Management for details.

Behavioral Differences

The following settings are recognized by both ADP and the core agent, but with different behavior or default values.

Config KeyDescriptionAgent BehaviorADP Behavior
dogstatsd_mapper_cache_sizeMapper result LRU cache size0 disables mapping; positive sizes the LRU0 disables the cache only; mapping still runs (#1687)
dogstatsd_metrics_stats_enableEnable per-metric debug statsConfig toggleGates debug log; stats API on-demand (#1352, #1356)
dogstatsd_stats_enableEnable internal stats endpointConfig toggleOn-demand via API (#1352)
dogstatsd_stats_bufferInternal stats buffer sizeConfigurableOn-demand via API (#1352)
dogstatsd_stats_portInternal stats endpoint portConfigurable portOn-demand via API (#1352)
log_levelLog verbosity directivesControls Agent logsPlain levels control ADP/Saluki-owned targets only
logging_frequencyTransaction success log intervalThrottles success logsIntentionally unused
min_tls_versionMinimum outbound TLS versionSupports TLS 1.0, 1.1, 1.2, and 1.3Supports TLS 1.2+ and TLS 1.3-only; clamps TLS 1.0/1.1 to 1.2
serializer_zstd_compressor_levelZstd compression levelDefault level 1Default level 3 (intentional)
skip_ssl_validationSkip TLS cert validationDisables validation for outbound HTTPS clientsApplies to the shared Datadog forwarder; rejected in FIPS mode

Datadog intake TLS protocol version (min_tls_version)

ADP supports min_tls_version for Datadog intake forwarding through the shared Datadog forwarder. The default is tlsv1.2, which allows TLS 1.2 and TLS 1.3. To require TLS 1.3 only, set min_tls_version: tlsv1.3 or DD_MIN_TLS_VERSION=tlsv1.3.

The core agent also accepts tlsv1.0 and tlsv1.1. ADP accepts those values for configuration compatibility, but clamps them to TLS 1.2 because ADP uses rustls, which doesn't support TLS 1.0 or TLS 1.1.

This setting doesn't affect ADP IPC, local privileged APIs, ADP control-plane clients, OTLP proxying to the core agent, or unrelated HTTP clients.

DogStatsD forwarding (statsd_forward_host / statsd_forward_port)

ADP supports DogStatsD forwarding when both statsd_forward_host and statsd_forward_port are set. ADP forwards each framed DogStatsD message over UDP to the configured destination before parsing, filtering, mapping, or aggregation. Forwarding doesn't preserve the core Agent's packet-buffer grouping, so forwarded UDP datagrams may be split differently while carrying the same DogStatsD messages. ADP logs setup failures and tracks send failures through telemetry.

Multi-region failover metrics

ADP supports multi-region failover for metrics. When multi_region_failover.enabled and multi_region_failover.failover_metrics are both true, ADP forwards metrics to the primary Datadog endpoint and to a second MRF endpoint.

To enable the MRF metrics branch at startup, configure multi_region_failover.api_key and one of multi_region_failover.site or multi_region_failover.dd_url. If the MRF endpoint configuration is incomplete, ADP skips the MRF branch and continues forwarding to the primary endpoint.

ADP does not fall back to the primary api_key, site, or dd_url for MRF traffic. multi_region_failover.enabled and endpoint selection are resolved at startup. multi_region_failover.failover_metrics, multi_region_failover.metric_allowlist, and multi_region_failover.api_key can refresh from live configuration after the MRF branch is enabled.

Config KeyBehaviorDefault
multi_region_failover.enabledEnables multi-region failover mode.false
multi_region_failover.failover_metricsEnables metrics forwarding to the failover region when MRF is enabled.false
multi_region_failover.metric_allowlistExact metric names to forward to MRF. Empty or unset forwards all metrics.[]
multi_region_failover.api_keyAPI key for the failover-region endpoint.unset
multi_region_failover.siteDatadog site for the failover region, used as https://app.mrf.<site>.unset
multi_region_failover.dd_urlExplicit failover intake URL. Takes precedence over site when set.unset

Datadog intake TLS validation (skip_ssl_validation)

ADP supports skip_ssl_validation for Datadog intake forwarding through the shared Datadog forwarder. The default is false, which preserves normal server certificate validation. To accept invalid server certificates for Datadog intake requests, set skip_ssl_validation: true or DD_SKIP_SSL_VALIDATION=true.

When enabled, this setting affects the Datadog intake clients used by metrics, logs, traces, events, and service checks that flow through the shared forwarder.

WARNING

Setting skip_ssl_validation: true disables TLS server certificate validation for Datadog intake forwarding. Use it only when you understand and accept that risk.

This setting does not affect ADP IPC, local privileged APIs, ADP control-plane clients, OTLP proxying to the core agent, or unrelated HTTP clients. In FIPS builds, ADP rejects skip_ssl_validation: true because disabling TLS certificate validation is not FIPS-compliant.

Logging verbosity (log_level / logging_frequency)

ADP accepts log_level as the startup logging control. A plain level applies to ADP-owned and Saluki-owned targets only, including agent_data_plane, saluki_*, and runtime crates under lib/.

yaml
log_level: debug

This keeps third-party dependencies such as hyper, tokio, and tonic at their default filtering unless you opt them in.

To control dependency logs or set a global fallback, use advanced EnvFilter directives in log_level. ADP applies those directive strings as configured:

yaml
log_level: warn,agent_data_plane=debug,hyper=warn

logging_frequency is intentionally unused by ADP. The core agent uses it to throttle repetitive successful transaction logs. ADP logs successful forwarder operations below the default info level, so there is no matching info-level success-log stream to throttle.

DogStatsD statistics (dogstatsd_stats_enable / dogstatsd_metrics_stats_enable)

The core agent has two DogStatsD statistics mechanisms with different scopes. dogstatsd_stats_enable enables packet-level throughput statistics from a ring buffer, exposed as Go expvar data on dogstatsd_stats_port (default 5000). Operators must configure an OpenMetrics check to scrape that endpoint before the data is submitted. dogstatsd_metrics_stats_enable enables runtime-toggleable metric-level debug statistics that track count and last-seen time per unique metric and tag combination. That data powers the core agent's dogstatsd-stats CLI command and HTTP endpoint.

ADP does not mirror the packet-level statistics config path. Instead, ADP provides an on-demand metric-level view through a DogStatsD statistics destination that is always wired into the topology, but only collects data during a time-bounded request. To collect statistics, run agent-data-plane dogstatsd stats --duration-secs N or call the privileged /dogstatsd/stats?collection_duration_secs=N API. The handler waits for the requested collection window, then returns count and last-seen time per metric context inline as JSON. The CLI uses the same API and renders the result as either summary or cardinality analysis.

ADP also exposes internal DogStatsD telemetry through its OpenMetrics endpoint, always-on at http://<api_listen_address>/metrics (the unprivileged API endpoint; default port 5100). Scrape that endpoint to collect aggregate DogStatsD counters such as processed message counts, packet and byte counts, packet pool usage, and channel latency. This endpoint is separate from /dogstatsd/stats: it does not return the per-metric count and last-seen map, and it is not controlled by the core agent's dogstatsd_stats_* keys.

ADP does not expose the core agent's packet-per-second expvar endpoint or a persistent per-metric DogStatsD statistics endpoint to scrape. You do not need to set up scraper configuration for this per-metric data. The config keys dogstatsd_stats_enable, dogstatsd_stats_buffer, and dogstatsd_stats_port have no effect in ADP. See #1352.

DogStatsD metric debug log

ADP supports the core agent's DogStatsD metric debug log. To write this file, set dogstatsd_metrics_stats_enable: true. dogstatsd_logging_enabled also must be true; it defaults to true, so most configurations only need to enable dogstatsd_metrics_stats_enable.

When dogstatsd_logging_enabled is true, ADP connects an extra DogStatsD destination to the decoded metric stream. The destination writes one line per metric sample with the metric name, tags, count, and last-seen time while dogstatsd_metrics_stats_enable is true. When dogstatsd_metrics_stats_enable is false, the destination drains decoded metrics and drops them. This lets runtime configuration changes start and stop the debug log without rebuilding the topology. This feature is for support and troubleshooting. It does not change normal metric forwarding, and it does not replace the on-demand /dogstatsd/stats API.

Use these settings to control the file:

Config KeyBehavior
dogstatsd_log_fileOutput path. If empty, ADP uses the platform default DogStatsD stats log path.
dogstatsd_log_file_max_rollsNumber of rotated files to keep. Defaults to 3.
dogstatsd_log_file_max_sizeMaximum active file size before rotation. Defaults to 10Mb.
dogstatsd_logging_enabledControls whether ADP wires the debug log destination into the topology. Defaults to true.

The default dogstatsd_log_file path is /var/log/datadog/dogstatsd_info/dogstatsd-stats.log on Linux and other Unix platforms, /opt/datadog-agent/logs/dogstatsd_info/dogstatsd-stats.log on macOS, and %ProgramData%\datadog\logs\dogstatsd_info\dogstatsd-stats.log on Windows.

This debug log differs from the dogstatsd_capture_* settings. The debug log records decoded metric summaries after DogStatsD parsing. The capture settings record raw DogStatsD traffic for packet-level investigation, and they remain tracked separately under #1381.

Payload debug logging (log_payloads)

ADP supports log_payloads for debugging metric, event, and service check payload contents before they enter Datadog encoders. To see these logs, set log_payloads: true and run with debug-level logging enabled.

When enabled, ADP logs decoded payload objects: scalar series metrics, sketches/distributions, events, and service checks. These logs can contain high-volume customer data, including metric names, tags, host and container metadata, event text, and service check messages. Use this setting only while diagnosing payload content.

ADP does not dump the exact encoded JSON or protobuf HTTP request body, and it does not log compressed wire payload bytes.

dogstatsd_mapper_cache_size

ADP and the core agent both cache mapper results to skip regex evaluation on repeat metric names. With the default value of 1000, and with any positive integer, behavior matches the core agent: results are cached in an LRU keyed by the original metric name, including a negative-cache entry for names that match no profile.

The two implementations diverge when this setting is 0. In the core agent, 0 is rejected by the underlying LRU library, which causes the entire mapper to be silently disabled: mapping profiles configured by dogstatsd_mapper_profiles are not applied. In ADP, 0 disables the result cache only; mapping profiles still run, so each metric pays the regex evaluation cost without amortization.

If you previously set dogstatsd_mapper_cache_size: 0 in the core agent to turn off the mapper, clear dogstatsd_mapper_profiles instead when running ADP. See #1687.

Heroku dyno telemetry (heroku_dyno)

The heroku_dyno setting affects the core Agent's self-telemetry heartbeat. It changes the Agent flavor used by the core Agent aggregator so the running heartbeat is emitted as datadog.heroku_agent.running.

ADP does not run in the supported Heroku Agent package path: the Heroku Agent package excludes the agent-data-plane dependency, and the Heroku Datadog launch script starts the core Agent, trace Agent, and optionally process Agent without launching an agent-data-plane process. ADP also does not emit the core Agent's datadog.<agentName>.running series.

Because the affected heartbeat is core-Agent-owned and ADP is not part of the supported Heroku deployment path, ADP does not implement heroku_dyno. See #1753.

Compatibility Unknown

The following settings need further investigation. ADP behavior may differ from the core agent in ways that are not yet fully characterized.

Config KeyDescriptionIssue
aggregator_buffer_sizeChannel buffer depth for aggregator queues#1681
aggregator_flush_metrics_and_serialize_in_parallel_buffer_sizeParallel flush: series/sketch buffer size#1681
aggregator_flush_metrics_and_serialize_in_parallel_chan_sizeParallel flush: channel size#1681
aggregator_stop_timeoutTimeout (s) for aggregator flush on stop#1681
aggregator_use_tags_storeEnable shared tag deduplication store#1681
anomaly_detection.enabledEnable anomaly detection observer pipeline#1683
anomaly_detection.metrics.enabledEnable metric ingestion for anomaly detection#1683
autoscaling.failover.enabledEnable autoscaling failover metric routing#1684
autoscaling.failover.metricsMetric names forwarded to DCA for failover#1684
dogstatsd_disable_verbose_logsSuppress noisy parse error logs#1350
dogstatsd_experimental_http.enabledEnable experimental HTTP/H2C DSD listener#1682
dogstatsd_experimental_http.listen_addressBind address for experimental HTTP DSD listener#1682
forwarder_apikey_validation_intervalAPI key check interval (minutes)#1357
forwarder_flush_to_disk_mem_ratioMem-to-disk flush threshold#1364
forwarder_high_prio_buffer_sizeHigh-priority request queue size#1362
forwarder_low_prio_buffer_sizeLow-priority request queue size#1362
forwarder_max_concurrent_requestsMax concurrent HTTP requests#1363
forwarder_requeue_buffer_sizeIn-memory re-queue buffer size#1755
forwarder_retry_queue_capacity_time_interval_secRetry queue time-based capacity#1365
forwarder_stop_timeoutTimeout (s) for forwarder graceful stop[#1680]
telemetry.dogstatsd.aggregator_channel_latency_bucketsHistogram buckets: DSD aggregator channel lag#1679
telemetry.dogstatsd.listeners_channel_latency_bucketsHistogram buckets: listener channel latency#1679
telemetry.dogstatsd.listeners_latency_bucketsHistogram buckets: listener processing#1679
telemetry.dogstatsd_originPer-origin processed-metrics telemetry#1679

ADP-Only Settings

The following settings are specific to ADP and have no equivalent in the core agent.

Config KeyDescriptionDefault
agent_ipc_endpointRemote agent IPC URI
aggregate_flush_intervalAggregator flush period
aggregate_flush_open_windowsFlush open windows on stop
aggregate_passthrough_idle_flush_timeoutPassthrough buffer flush delay
aggregate_window_duration_secondsAggregation window size
connect_retry_attemptsIPC client connect retries
connect_retry_backoffIPC client retry delay
counter_expiry_secondsIdle counter keep-alive duration300
data_plane.api_listen_addressADP unprivileged API address
data_plane.dogstatsd.aggregator_tag_filter_cache_capacityTag-filter deduplication cache size100000
data_plane.remote_agent_enabledRegister as remote agent
data_plane.secure_api_listen_addressADP privileged API address
data_plane.standalone_modeADP standalone mode toggle
data_plane.use_new_config_stream_endpointUse new config stream endpoint
dogstatsd_allow_context_heap_allocsAllow heap allocations for contexts
dogstatsd_autoscale_udp_listenersBind multiple UDP sockets via SO_REUSEPORT
dogstatsd_buffer_countNumber of receive buffers
dogstatsd_cached_contexts_limitMax cached metric contexts
dogstatsd_cached_tagsets_limitMax cached tagsets
dogstatsd_mapper_string_interner_sizeMapper string interner capacity
dogstatsd_minimum_sample_rateFloor for metric sample rates
dogstatsd_permissive_decodingRelaxes decoder strictnesstrue
dogstatsd_string_interner_size_bytesExplicit byte budget for context interner
dogstatsd_tcp_portTCP listen port for DSD
enable_global_limiterToggle global memory limiter
flush_timeout_secsEncoder flush timeout (secs)
memory_limitProcess memory limit (bytes)
memory_modeADP global memory limiter mode
memory_slop_factorMemory headroom fraction
metrics_levelADP internal metrics emission level
otlp_string_interner_sizeOTLP context interner capacity
remote_agent_string_interner_size_bytesTag string interner capacity512 KB
serializer_max_metrics_per_payloadMax metrics per payload
statsd_metric_namespace_blocklistRenamed alias for blacklist key

memory_limit / memory_slop_factor

ADP uses an explicit process memory limit (memory_limit) rather than relying on Go's garbage collector. The memory_slop_factor reserves a fraction of the limit to account for allocations not tracked by ADP's internal accounting. When memory usage approaches memory_limit, ADP's global limiter begins exerting backpressure (see enable_global_limiter).

dogstatsd_minimum_sample_rate

ADP enforces a minimum sample rate on incoming metrics to prevent memory exhaustion from extremely low sample rates on histograms and sketches. Sending metrics with a very high inverse sample rate (for example @0.0000001) can cause unbounded memory growth in a sketch; this setting prevents that. The default is conservative enough that normal clients are unaffected.

dogstatsd_permissive_decoding

By default, ADP parses DogStatsD packets with the same leniency as the core agent, accepting packets that technically violate the spec. Setting this to false enables strict mode, which rejects non-conformant packets. Strict mode is not available in the core agent.

data_plane.remote_agent_enabled / data_plane.use_new_config_stream_endpoint

These two keys are transitional flags being phased out. Both will be implied by data_plane.standalone_mode=false in a future release. Do not rely on them for new deployments.

Transparent Settings

The following settings work in ADP with the same behavior as the core agent.

To enable syslog logging, set log_to_syslog: true. Console logging remains controlled by log_to_console; enabling syslog does not disable console or file logging. If syslog_uri is empty while syslog logging is enabled, ADP uses the platform default local syslog socket: unixgram:///dev/log on Linux and unixgram:///var/run/syslog on macOS. Set syslog_rfc: true when the receiving syslog daemon expects the Agent's RFC-style header.

Config KeyDescription
additional_endpointsDual-ship to extra endpoints
aggregate_context_limitMax contexts per aggregation window
allow_arbitrary_tagsRelax backend tag validation via HTTP header
api_keyAPI key for endpoint auth
auth_token_file_pathIPC auth token file path
bind_hostGlobal listen host fallback
cmd_portAgent IPC/CMD API port
container_cgroup_rootCgroup filesystem root path
container_proc_rootProcfs root path for containers
cri_connection_timeoutCRI runtime connection timeout (s)
cri_query_timeoutCRI runtime query timeout (s)
cri_socket_pathCRI/containerd socket path
data_plane.dogstatsd.enabledEnable DSD in data plane
data_plane.enabledEnable ADP globally
dd_urlOverride intake endpoint URL
dogstatsd_buffer_sizeReceive buffer size (bytes)
dogstatsd_context_expiry_secondsContext cache TTL (seconds)
dogstatsd_entity_id_precedenceEntity ID over auto-detection
dogstatsd_eol_requiredRequire newline-terminated messages
dogstatsd_expiry_secondsCounter zero-value TTL (secs)
dogstatsd_flush_incomplete_bucketsFlush open buckets on shutdown
dogstatsd_log_fileDSD metric debug log path
dogstatsd_log_file_max_rollsMax rotated DSD debug log files
dogstatsd_log_file_max_sizeMax DSD debug log file size
dogstatsd_logging_enabledEnable DSD metric debug logging
dogstatsd_mapper_profilesMetric mapping profile definitions
dogstatsd_no_aggregation_pipelineEnable no-aggregation timestamped path
dogstatsd_non_local_trafficAccept non-localhost UDP/TCP
dogstatsd_origin_detectionEnable UDS origin detection
dogstatsd_origin_detection_clientHonor client origin proto fields
dogstatsd_origin_optout_enabledAllow clients to opt out origin
dogstatsd_portUDP listen port
dogstatsd_so_rcvbufSocket receive buffer size
dogstatsd_socketUDS datagram socket path
dogstatsd_stream_log_too_bigLog oversized UDS stream frames
dogstatsd_stream_socketUDS stream socket path
dogstatsd_string_interner_sizeString interner capacity
dogstatsd_tag_cardinalityDefault tag cardinality level
dogstatsd_tagsExtra tags added to all DSD data
enable_payloads.eventsAllow sending event payloads
enable_payloads.seriesAllow sending series payloads
enable_payloads.service_checksAllow sending service check payloads
enable_payloads.sketchesAllow sending sketch payloads
expected_tags_durationHost tag enrichment duration
extra_tagsAdditional static tags
forwarder_backoff_baseRetry backoff base (secs)
forwarder_backoff_factorRetry backoff jitter factor
forwarder_backoff_maxRetry backoff ceiling (secs)
forwarder_connection_reset_intervalHTTP conn reset interval (secs)
forwarder_num_workersConcurrent forwarder workers
forwarder_recovery_intervalBackoff recovery decrease factor
forwarder_recovery_resetReset errors on success
forwarder_retry_queue_max_sizeRetry queue max size (deprecated)
forwarder_retry_queue_payloads_max_sizeRetry queue max size (bytes)
forwarder_storage_max_disk_ratioMax disk usage ratio for retry
forwarder_storage_max_size_in_bytesMax on-disk retry storage size
forwarder_storage_pathOn-disk retry storage directory
forwarder_timeoutForwarder HTTP request timeout
histogram_aggregatesHistogram aggregate statistics
histogram_copy_to_distributionCopy histograms to distributions
histogram_copy_to_distribution_prefixPrefix for hist-to-dist copies
histogram_percentilesHistogram percentile quantiles
hostnameConfigured hostname override
ipc_cert_file_pathIPC TLS certificate path
log_fileLog output file path
log_file_max_rollsMax rotated log files kept
log_file_max_sizeMax log file size before rotate
log_format_jsonUse JSON log format
log_payloadsDebug-log decoded payload contents
log_to_consoleLog to stdout/stderr
log_to_syslogLog to syslog daemon
metric_filterlistMetric name blocklist
metric_filterlist_match_prefixBlocklist uses prefix matching
metric_tag_filterlistPer-metric tag include/exclude
no_proxy_nonexact_matchDomain/CIDR no_proxy matching
observability_pipelines_worker.metrics.enabledRoute metrics to OPW instance
observability_pipelines_worker.metrics.urlOPW metrics intake URL
origin_detection_unifiedUnified origin detection mode
provider_kindProvider kind static tag
proxyHTTP/HTTPS proxy configuration
run_pathRuntime data directory path
secret_backend_commandSecret resolver executable path
secret_backend_timeoutSecret backend timeout (seconds)
serializer_compressor_kindPayload compression algorithm
serializer_max_payload_sizeMax compressed payload size
serializer_max_series_payload_sizeMax series compressed payload size
serializer_max_series_points_per_payloadMax data points per series payload
serializer_max_series_uncompressed_payload_sizeMax series uncompressed payload size
serializer_max_uncompressed_payload_sizeMax uncompressed payload size
siteDatadog site domain
statsd_metric_blocklistMetric name blocklist
statsd_metric_blocklist_match_prefixBlocklist uses prefix matching
statsd_metric_namespacePrefix prepended to all metrics
statsd_metric_namespace_blacklistNamespace prefixes exempt (alias)
syslog_rfcUse RFC-style syslog header
syslog_uriSyslog destination URI
tagsGlobal tags (DD_TAGS)
use_proxy_for_cloud_metadataProxy cloud metadata endpoints
use_v2_api.seriesSend series via V2 protobuf endpoint
vector.metrics.enabledRoute metrics to OPW (legacy alias)
vector.metrics.urlOPW metrics intake URL (legacy alias)