Top-level Datadog configuration: API keys, service identity, Agent connection, intake site, hostname, global tags, and proxy settings.

DD_AGENT_HOST

Type: string
Overrides the default trace Agent host address for trace submission. Ignored if DD_TRACE_AGENT_URL is set.

DD_API_KEY

Type: string
Aliases:DATADOG_API_KEY
Sets the Datadog API key used to authenticate outbound requests when running in agentless mode (sending data directly to Datadog without a local Agent). Required for agentless CI test reporting and LLM Observability agentless mode.

DD_APM_TRACING_ENABLED

Type: boolean
Default: true
Aliases:DD_TRACING_ENABLED
Enables or disables sending APM trace data. When disabled, tracing still runs to support other products, but only periodic heartbeat traces and manually kept traces are sent.

DD_ENV

Type: string
Sets the global env tag applied to all telemetry emitted by the tracer (traces, metrics, logs, profiles). Use it to separate environments such as prod, staging, or dev.

DD_PROXY_NO_PROXY

Type: string
Configuration key to set a list of hosts that should bypass the proxy. The list is space-separated. For CI Visibility only

DD_SERVICE

Type: string
Aliases:DD_SERVICE_NAME, OTEL_SERVICE_NAME

Sets the service name used as the service tag on every span. If not specified, the SDK tries to determine the service name automatically.

Language-specific notes:

• .NET: falls back to the IIS application name, process entry assembly, or process name.
• Java: falls back to the Java agent’s auto-detected service name based on the application class.
• Node.js: falls back to the name field in package.json.

DD_SERVICE_MAPPING

Type: map
Define service name mappings to allow renaming services in traces, for example: postgres:postgresql,defaultdb:postgresql. Available in version 0.47+.

DD_SITE

Type: string
Default: datadoghq.com
Sets the site domain used to build agentless intake URLs. If unset, a default site is used.

DD_TAGS

Type: map
Custom tags applied to traces, profiles, and metrics, provided as comma-separated key:value pairs (for example, layer:api,team:intake).

DD_VERSION

Type: string

Sets the application’s version, used as the version tag in traces and logs (for example: 1.2.3, 6c44da20, 2020.02.13).

Language-specific notes:

• PHP: starting with version 0.90.0, changes made at runtime through ini_set('datadog.version', ...) are also applied to the current root span.

Core distributed tracing engine: Agent connection, trace and span ID generation, span lifecycle management, peer service mapping, resource normalization, query string obfuscation, and DB client configuration.

DD_HTTP_CLIENT_ERROR_STATUSES

Type: string
Default: 400-499
Client HTTP status codes that mark spans as errors.

DD_HTTP_SERVER_ERROR_STATUSES

Type: string
Default: 500-599
Server HTTP status codes that mark spans as errors.

DD_TRACE_128_BIT_TRACEID_GENERATION_ENABLED

Type: boolean
Default: true
Controls whether the tracer generates 128-bit W3C trace IDs (32-character hex) or 64-bit Datadog trace IDs (16-character hex). 128-bit IDs are required for full W3C traceparent interoperability.

DD_TRACE_128_BIT_TRACEID_LOGGING_ENABLED

Type: boolean
Default: true
Controls whether 128-bit trace IDs are logged in their full 32-character format or truncated to 16 characters. Set to false for compatibility with systems that expect the shorter format.

DD_TRACE_AGENT_ARGS

Type: string
Azure App Services: extra command-line arguments for launching the external trace-agent process (whitespace/comma-separated). If unset, no extra args are passed.

DD_TRACE_AGENT_PATH

Type: string
Azure App Services: path to the external trace-agent executable to launch. If unset, the tracer will not start the external trace-agent process.

DD_TRACE_AGENT_PORT

Type: int
Default: -1
Aliases:DD_AGENT_PORT
Sets the port where profiles are sent (the port where the Agent is listening for connections). Ignored if DD_TRACE_AGENT_URL is set. Defaults to8126.

DD_TRACE_AGENT_PROTOCOL_VERSION

Type: string
Default: 0.4
Since: v1.62.0
Protocol version to use for requests to the agent. The version configured must be supported by the agent version installed or all traces will be dropped.

DD_TRACE_AGENT_TIMEOUT

Type: int
Default: 10
Timeout in seconds for network interactions with the Datadog Agent.

DD_TRACE_AGENT_UNIX_DOMAIN_SOCKET

Type: string
This can be used to direct trace traffic to a proxy, to later be sent to a remote Datadog Agent.

DD_TRACE_AGENT_URL

Type: string
Aliases:DD_TRACE_URL
Sets the URL endpoint where traces are sent. Overrides DD_AGENT_HOST and DD_TRACE_AGENT_PORT if set. Defaults to http://<DD_AGENT_HOST>:<DD_TRACE_AGENT_PORT> .

DD_TRACE_ANALYTICS_ENABLED

Type: boolean
Default: false
Since: v1.55.0
Enables the legacy Trace Analytics feature for all integrations by setting the analytics.sample_rate metric on spans using each integration’s configured analytics sample rate. Superseded by App Analytics in newer Datadog deployments.

DD_TRACE_CLASSES_EXCLUDE

Type: string
A list of fully qualified classes (that may end with a wildcard to denote a prefix) which will be ignored (not modified) by the tracer. Must use the jvm internal representation for names (eg package.ClassName$Nested and not package.ClassName.Nested)

DD_TRACE_CLIENT_IP_ENABLED

Type: boolean
Default: false
Enables or disables the automatic collection of client IP addresses from HTTP request headers. When enabled, the IP address is stored in the http.client_ip span tag.

DD_TRACE_CLIENT_IP_HEADER

Type: string
Configures a custom header name from which to source the http.client_ip tag value. If this variable is set, all other IP-related headers are ignored (for example, setting DD_TRACE_CLIENT_IP_HEADER=custom-ip-header and including the header custom-ip-header: 5.6.7.9 in a request results in a span tagged with “http.client_ip”: “5.6.7.9”). If an empty string or null value is passed, IP headers are queried in this order: - x-forwarded-for - x-real-ip - true-client-ip - x-client-ip - x-forwarded - forwarded-for - x-cluster-client-ip - fastly-client-ip - cf-connecting-ip - cf-connecting-ipv6

DD_TRACE_CLOUD_PAYLOAD_TAGGING_MAX_DEPTH

Type: int
Default: 10
An integer representing the maximum depth of an AWS SDK request/reponse payload to use for AWS payload tagging.

DD_TRACE_CLOUD_PAYLOAD_TAGGING_MAX_TAGS

Type: int
Default: 758
An integer representing the maximum number of tags to extract per a span to be used for AWS payload tagging.

DD_TRACE_CLOUD_PAYLOAD_TAGGING_SERVICES

Type: string
Default: ["S3", "Sqs", "Kinesis", "Sns", "DynamoDB", "ApiGatewayV2", "EventBridge", "ApiGateway"]
To enable AWS payload tagging for additional services, use this setting.

DD_TRACE_CLOUD_REQUEST_PAYLOAD_TAGGING

Type: array
A comma-separated string of JSONPath entries to redact from AWS SDK requests. Setting this enables AWS payload tagging for requests.

DD_TRACE_CLOUD_RESPONSE_PAYLOAD_TAGGING

Type: array
A comma-separated string of JSONPath entries to redact from AWS SDK responses. Setting this enables AWS payload tagging for responses.

DD_TRACE_CONFIG

Type: string
Path to valid Java properties file which contains the agent configuration Notes: When OTEL_JAVAAGENT_CONFIGURATION_FILE and DD_TRACE_CONFIG are both set we apply the configuration from both files. This is an exception to the usual rule where the Datadog setting overrides the OTel one

DD_TRACE_DB_CLIENT_SPLIT_BY_HOST

Type: boolean
Default: false
When set to true db spans get assigned the remote database hostname as the service name

DD_TRACE_DB_CLIENT_SPLIT_BY_INSTANCE

Type: boolean
Default: false
Set the service name of HTTP requests to pdo- . For example, a PDO->query() call to a database host datadoghq.com has the service name pdo-datadoghq.com instead of the default service name of pdo.

DD_TRACE_ENABLED

Type: boolean
Default: true
Aliases:DD_TRACING_ENABLED
Enable framework and library instrumentation. When false, the application code doesn’t generate any traces. See also DD_APM_TRACING_ENABLED.

DD_TRACE_EXPERIMENTAL_FEATURES_ENABLED

Type: string
Supported Input: A comma-separated list of configuration options that support experimental features. Supported Values: all, DD_TAGS (Java, .NET) Caveats: Only supported in Java and .NET Description: Enables experimental features for specific configuration options. When enabled, these features may provide additional functionality but are not yet considered stable and may change or be removed in future releases. You can enable all experimental features using the keyword all, or list individual features explicitly.

DD_TRACE_FLUSH_INTERVAL

Type: decimal
Default: 1.0
Trace writer flush interval (seconds): controls how often the tracer flushes/sends traces. Default: 1.0s.

DD_TRACE_GLOBAL_TAGS

Type: map
Global tags: key/value tags applied everywhere (on all spans and runtime metrics). Merged from dd.trace.global.tags (legacy) and dd.tags/dd.trace.tags (and adjusted by DD_ENV/DD_VERSION). Default: empty.

DD_TRACE_HEALTH_METRICS_ENABLED

Type: boolean
Default: true
When set to true sends tracer health metrics

DD_TRACE_HEALTH_METRICS_STATSD_HOST

Type: string
Statsd host to send health metrics to

DD_TRACE_HEALTH_METRICS_STATSD_PORT

Type: int
Statsd port to send health metrics to

DD_TRACE_JMX_TAGS

Type: map
A list of span tags to be added to every jmx metric.

DD_TRACE_METHODS

Type: string

List of methods to trace. Accepts a semicolon (;) separated list where each entry has the format Namespace.TypeName[MethodNames], where MethodNames is either a comma (,) separated list of method names or the * wildcard.

For generic types, replace the angled brackets and the type parameters’ names with a backtick (`) followed by the number of generic type parameters. For example, Dictionary<TKey, TValue> must be written as Dictionary`2. For generic methods, you only need to specify the method name.

Note: The wildcard method support ([*]) selects all methods in a type except constructors, property getters and setters, Equals, Finalize, GetHashCode, and ToString

DD_TRACE_OBFUSCATION_QUERY_STRING_REGEXP

Type: string
Aliases:DD_OBFUSCATION_QUERY_STRING_REGEXP
A regex to redact sensitive data from incoming requests’ query string reported in the http.url tag (matches are replaced with ).

DD_TRACE_PARTIAL_FLUSH_ENABLED

Type: boolean
Default: true
Enables incrementally flushing large traces to the Datadog Agent, reducing the chance of rejection by the Agent. Use only when you have long-lived traces or traces with many spans. Valid values are true or false. Added in version 1.26.0, only compatible with the Datadog Agent 7.26.0+.

DD_TRACE_PARTIAL_FLUSH_MIN_SPANS

Type: int
Default: 1000
Minimum number of finished spans accumulated in a trace before a partial flush is triggered. Invalid values are ignored.

DD_TRACE_PEER_SERVICE_DEFAULTS_ENABLED

Type: boolean
Default: false
When enabled, the tracer computes default peer.service values for eligible spans using the v1 peer-service default algorithm under Naming Schema v0. When disabled, Naming Schema v0 leaves peer.service unset.

DD_TRACE_PEER_SERVICE_MAPPING

Type: map
Maps detected peer service names to normalized values before they are attached to spans.

DD_TRACE_PIPE_NAME

Type: string
Datadog Agent named pipe: sets the Windows named pipe name/path used as the HTTP transport to communicate with the Datadog Agent (instead of TCP or a Unix domain socket). When set, the tracer’s HTTP client uses a NamedPipe socket factory. Default: unset.

DD_TRACE_RABBIT_PROPAGATION_ENABLED

Type: boolean
Default: true
Aliases:DD_RABBIT_PROPAGATION_ENABLED
Rabbit (RabbitMQ) context propagation: when enabled, injects and extracts trace context via AMQP message headers so traces can continue across publish/consume. This also gates injecting the tracer’s RabbitMQ time-in-queue timestamp header. Default: true.

DD_TRACE_REMOVE_INTEGRATION_SERVICE_NAMES_ENABLED

Type: boolean
Default: false
When enabled, integrations under Naming Schema v0 stop using inferred service names and fall back to the application service name. Use this to make all spans report under DD_SERVICE regardless of integration.

DD_TRACE_REPORT_HOSTNAME

Type: boolean
Default: false
Whether to report the system’s hostname for each trace. When disabled, the hostname of the Agent is used instead.

DD_TRACE_RESOURCE_RENAMING_ALWAYS_SIMPLIFIED_ENDPOINT

Type: boolean
Default: false
Since: v1.60.0
When enabled, always sets the http.endpoint tag to the result of the Resource Renaming simplification algorithm, even when an explicit endpoint is available.

DD_TRACE_RESOURCE_RENAMING_ENABLED

Type: boolean
Default: false
Since: v1.60.0
Controls whether the http.endpoint tag is computed and added for incoming HTTP requests. This is disabled by default unless application security is enabled at startup, and can be explicitly enabled or disabled with this setting.

DD_TRACE_SECURE_RANDOM

Type: boolean
Default: false
Secure random ID generation: when enabled, forces the tracer to use the SECURE_RANDOM ID generation strategy (based on SecureRandom) for trace/span IDs. This is also forced on AWS Lambda SnapStart (AWS_LAMBDA_INITIALIZATION_TYPE=snap-start). Default: false.

DD_TRACE_SPAN_ATTRIBUTE_SCHEMA

Type: string
Default: v0
Selects the span attribute and naming schema version used by integrations. Accepted values: v0, v1.

DD_TRACE_SPAN_TAGS

Type: map
A list of default tags to be added to every span.

DD_TRACE_SPLIT_BY_TAGS

Type: string
Used to rename the service name associated with spans to be identified with the corresponding span tag

DD_TRACE_STATS_COMPUTATION_ENABLED

Type: boolean
Default: true
Since: v1.55.0
Aliases:DD_TRACE_TRACER_METRICS_ENABLED
Controls whether client-side trace statistics computation is enabled. When enabled, the tracer pre-aggregates span stats for ingestion.

DD_TRACE_TAGS

Type: map
Aliases:DD_TAGS
A list of default tags to be added to every span, profile, and JMX metric. If DD_ENV or DD_VERSION is used, it overrides any env or version tag defined in DD_TAGS. Available for versions 0.50.0+.

DD_TRACE_TRACE_CONFIG_ANALYTICS_ENABLED

Type: boolean
Default: false
Aliases:DD_TRACE_CONFIG_ANALYTICS_ENABLED
Enables trace analytics for spans produced by the TraceConfig integration

DD_TRACE_TRACE_CONFIG_ANALYTICS_SAMPLE_RATE

Type: decimal
Default: 1.0
Aliases:DD_TRACE_CONFIG_ANALYTICS_SAMPLE_RATE
Sampling rate for analytics events generated by the TraceConfig integration

DD_TRACE_TRACE_CONFIG_ENABLED

Type: boolean
Default: true
Aliases:DD_TRACE_INTEGRATION_TRACE_CONFIG_ENABLED, DD_INTEGRATION_TRACE_CONFIG_ENABLED
Enables Trace Config (TraceConfig) instrumentation

DD_TRACE_TRACE_ENABLED

Type: boolean
Default: true
Aliases:DD_INTEGRATION_TRACE_ENABLED, DD_TRACE_INTEGRATION_TRACE_ENABLED
Enables method tracing via trace annotations and configured trace methods (creates spans for methods annotated with datadog.trace.api.Trace and other supported @Trace annotations, and for class/methods listed in tracer configuration)

DD_TRACE_X_DATADOG_TAGS_MAX_LENGTH

Type: int
Default: 512
Maximum length of the x-datadog-tags header for trace tag propagation. Set to 0 to disable.

DD_WRITER_TYPE

Type: string
Default: DDAgentWriter
Default value sends traces to the Agent. Configuring with LoggingWriter instead writes traces out to the console.

Sampling rules and rates that determine which traces and spans are kept or dropped, including per-service rules, rate limiting, and priority sampling.

DD_SPAN_SAMPLING_RULES

Type: string
Span sampling: JSON rules used to decide per-span sampling priority (single-span sampling). If both DD_SPAN_SAMPLING_RULES and DD_SPAN_SAMPLING_RULES_FILE are set, the file setting is ignored. Rules can match spans by service/name and apply a sample rate and optional max-per-second limit.

DD_SPAN_SAMPLING_RULES_FILE

Type: string
Points to a JSON file that contains the span sampling rules. DD_SPAN_SAMPLING_RULES takes precedence over this variable. See DD_SPAN_SAMPLING_RULES for the rule format.

DD_TRACE_RATE_LIMIT

Type: int
Default: 100
Sets the maximum number of traces to sample per second; applies only when either DD_TRACE_SAMPLING_RULES or DD_TRACE_SAMPLE_RATE is set.

DD_TRACE_SAMPLE_RATE

Type: decimal
Aliases:OTEL_TRACES_SAMPLER
Controls the ingestion sample rate (between 0.0 and 1.0) between the Agent and the backend. Use OTEL_TRACES_SAMPLER as an alias

DD_TRACE_SAMPLING_RULES

Type: string
JSON array of sampling rules. The rule is matched in order of specification. The first match in a list is used. Per entry: The item “sample_rate” is required in decimal format. The item “service” is optional in regular expression format, to match on service name. The item “name” is optional in regular expression format, to match on operation name. To give a rate of 50% to any traces in a service starting with the text “cart”: ‘[{“sample_rate”:0.5, “service”:“cart.”}]’ To give a rate of 20% to any traces which have an operation name of “http.request”: ‘[{“sample_rate”:0.2, “name”:“http.request”}]’ To give a rate of 100% to any traces within a service named “background” and with an operation name of “sql.query”: ‘[{“sample_rate”:1.0, “service”:“background”, “name”:“sql.query”}] To give a rate of 10% to all traces ‘[{“sample_rate”:0.1}]’ To configure multiple rules, separate by semi-colon and order from most specific to least specific: ‘[{“sample_rate”:0.5, “service”:“cart.”}, {“sample_rate”:0.2, “name”:“http.request”}, {“sample_rate”:1.0, “service”:“background”, “name”:“sql.query”}, {“sample_rate”:0.1}]’ If no rules are specified, or none match, default internal sampling logic will be used.

DD_TRACE_WEBSOCKET_MESSAGES_INHERIT_SAMPLING

Type: boolean
Default: true
By default, websocket messages preserve the same sampling as the span captured during the handshake. This ensures that, if a handshake span has been sampled, all the messages in its session will also be sampled. To disable that behavior and sample each websocket message independently, set this configuration to false.

Distributed trace context propagation, extraction and injection behavior, baggage handling, header tagging, HTTP client and server configuration, and SQL comment injection for Database Monitoring.

DD_DBM_ALWAYS_APPEND_SQL_COMMENT

Type: boolean
Default: false
Since: v1.55.0
When the DD_DBM_PROPAGATION_MODE is set, a comment is injected in SQL queries. Most of the time it is prepended. This config forces the comment to be appended at all times.

DD_EXPERIMENTAL_PROPAGATE_PROCESS_TAGS_ENABLED

Type: boolean
Default: true
Controls whether process-level tags (such as entrypoint metadata) are collected and attached to tracing payloads.

DD_HTTP_SERVER_ROUTE_BASED_NAMING

Type: boolean
Default: true
When set to false http framework routes are not used for resource names. This can change resource names and derived metrics if changed.

DD_HTTP_SERVER_TAG_QUERY_STRING

Type: boolean
Default: true
Enables or disables reporting the query string on server spans. Default value is true.

DD_PROPAGATION_STYLE_EXTRACT

Type: string
A comma-separated list of header formats from which to attempt to extract distributed tracing propagation data. The first format found with complete and valid headers is used to define the trace to continue. Deprecated since version 1.9.0

DD_PROPAGATION_STYLE_INJECT

Type: string
A comma-separated list of header formats to include to propagate distributed traces between services. Deprecated since version 1.9.0

DD_TRACE_BAGGAGE_MAX_BYTES

Type: int
Default: 8192
Configuration key to set the maximum number of bytes that can be injected into the baggage header when propagating to a downstream service. Default value is 8192 bytes.

DD_TRACE_BAGGAGE_MAX_ITEMS

Type: int
Default: 64
Configuration key to set the maximum number of items that can be injected into the baggage header when propagating to a downstream service. Default value is 64 items.

DD_TRACE_BAGGAGE_TAG_KEYS

Type: array
Default: ["user.id", "session.id", "account.id"]
Supported Input: A comma-separated string representing a list of case-sensitive baggage keys Caveats: Not supported in C++ Description: A comma-separated list of baggage keys that are automatically applied as span tags to the local root span. For example, a baggage key user.id is tagged as baggage.user.id This feature only applies to baggage extracted from incoming HTTP headers. Baggage set with the baggage API is not included. - To tag all baggage items, set the value to *. Use this with caution to avoid exposing sensitive data in tags. - To disable this feature, set the value to an empty string.

DD_TRACE_HEADER_BAGGAGE

Type: map
Accepts a map of case-insensitive header keys to baggage keys and automatically applies matching request header values as baggage on traces. On propagation the reverse mapping is applied: Baggage is mapped to headers. Available since version 1.3.0.

DD_TRACE_HEADER_TAGS

Type: map
Since: v1.57.0
Automatically apply specified HTTP headers as span tags. If a custom tag name is not specified, the tag key defaults to http.request.headers. for request headers and http.response.headers. for response headers.

DD_TRACE_HTTP_CLIENT_ERROR_STATUSES

Type: string
Default: 400-499
Aliases:DD_HTTP_CLIENT_ERROR_STATUSES
Comma-separated list of HTTP status codes and ranges to treat as errors for HTTP client spans (for example, 400-499,500). When set, matching responses mark the span as an error.

DD_TRACE_HTTP_CLIENT_PATH_RESOURCE_NAME_MAPPING

Type: map
Maps HTTP client request paths to custom resource names. Uses the same format as dd.trace.http.server.path-resource-name-mapping, but applies to HTTP client spans instead of server spans.

DD_TRACE_HTTP_CLIENT_SPLIT_BY_DOMAIN

Type: boolean
Default: false
Set the service name of HTTP requests to host- , for example a curl_exec() call to https://datadoghq.com has the service name host-datadoghq.com instead of the default service name of curl.

DD_TRACE_HTTP_CLIENT_TAG_QUERY_STRING

Type: boolean
Default: true
Aliases:DD_HTTP_CLIENT_TAG_QUERY_STRING
By default, query string parameters and fragments are added to the http.url tag on web client spans. Set to false to prevent the collection of this data.

DD_TRACE_HTTP_SERVER_ERROR_STATUSES

Type: string
Default: 500-599
Aliases:DD_HTTP_SERVER_ERROR_STATUSES
Comma-separated list of HTTP status codes or ranges treated as errors for HTTP server spans (for example, 500-599,404). Overrides the default behavior of flagging only 5xx responses as errors.

DD_TRACE_HTTP_SERVER_PATH_RESOURCE_NAME_MAPPING

Type: map
Maps HTTP request paths to custom resource names. Provide a comma-separated list of pattern:resource_name pairs:    – pattern: An Ant-style path pattern that must match the value of the http.path_group span tag.    – resource_name: The custom resource name to assign if the pattern matches. If * is used as the resource_name for a matching pattern, the original, unnormalized request path combined with the HTTP method is used as the resource name. For example, given the rule /test/**:*, a GET request for /test/some/path results in the resource name GET /test/some/path. Mappings are evaluated in order of priority, and the first matching rule applies. Unmatched request paths use the default normalization behavior. Request path | Resource path ———— | ————- /admin/index.jsp | /admin-page /admin/user/12345/delete | /admin/user /user/12345 | /user/?

DD_TRACE_INFERRED_PROXY_SERVICES_ENABLED

Type: boolean
Default: false
Since: v1.55.0
Aliases:DD_TRACE_INFERRED_SPANS_ENABLED
When enabled, the tracer registers the inferred-proxy propagator, which reads x-dd-proxy* headers (currently x-dd-proxy=aws-apigateway) and starts an inferred proxy span as the parent of the server span, using header values for service, resource, and tags.

DD_TRACE_PROPAGATION_BEHAVIOR_EXTRACT

Type: string
Default: continue
Specifies how incoming distributed tracing headers should be handled at a service level. Accepted values are: continue: The SDK will continue the distributed trace if the incoming distributed tracing headers represent a valid trace context. restart: The SDK will always start a new trace. If the incoming distributed tracing headers represent a valid trace context, that trace context will be represented as a span link on service entry spans (as opposed to the parent span in the continue configuration). ignore: The SDK will always start a new trace and all incoming distributed tracing headers are ignored.

DD_TRACE_PROPAGATION_EXTRACT_FIRST

Type: boolean
Default: false
When set to true, stops extracting after the first successful trace context extraction.

DD_TRACE_PROPAGATION_STYLE

Type: string
Specifies trace context propagation formats for extraction and injection in a comma-separated list. May be overridden by extract-specific or inject-specific configurations.

DD_TRACE_PROPAGATION_STYLE_EXTRACT

Type: string
A comma-separated list of propagation styles to use for extraction. When set, this overrides DD_TRACE_PROPAGATION_STYLE for extraction.

DD_TRACE_PROPAGATION_STYLE_INJECT

Type: string
Configuration: tracePropagationStyle.inject A comma-separated list of header formats to include to propagate distributed traces between services.

DD_TRACE_REQUEST_HEADER_TAGS

Type: map
Accepts a map of case-insensitive header keys to tag names and automatically applies matching request header values as tags on traces. Also accepts entries without a specified tag name that are automatically mapped to tags of the form http.request.headers.<header-name>. Available since version 0.96.0.

DD_TRACE_RESPONSE_HEADER_TAGS

Type: map
Accepts a map of case-insensitive header keys to tag names and automatically applies matching response header values as tags on traces. Also accepts entries without a specified tag name that are automatically mapped to tags of the form http.response.headers.<header-name>. Available since version 0.96.0.

Per-integration tracing configuration: enable/disable, analytics, service name, peer service overrides for library integrations and controls for disabling specific instrumentations.

General Integration Settings

DD_EXPERIMENTAL_DEFER_INTEGRATIONS_UNTIL

Type: string
Instrumentation (experimental): defers integration matching/activation until a configured delay (parsed as a simple duration). When the delay is recognized and 5 seconds, deferred matching is resumed later via a scheduled task.

DD_INTEGRATIONS_ENABLED

Type: boolean
Default: true
Tracer: global toggle for automatic instrumentation integrations. When disabled, integrations are not enabled by default (effectively disabling auto-instrumentation unless explicitly enabled). Default: true.

DD_JDK_SOCKET_ENABLED

Type: boolean
Default: true
Enable native JDK support for Unix Domain Sockets.

DD_JMXFETCH_CHECK_PERIOD

Type: int
How often to send JMX metrics (in ms).

DD_JMXFETCH_CONFIG

Type: string
Additional metrics configuration file for JMX metrics collection. The Java Agent looks for jvm_direct:true in the instance section in the yaml file to change configuration.

DD_JMXFETCH_CONFIG_DIR

Type: string
Additional configuration directory for JMX metrics collection. The Java Agent looks for jvm_direct:true in the instance section in the yaml file to change configuration.

DD_JMXFETCH_ENABLED

Type: boolean
Default: true
Enable collection of JMX metrics by Java Tracing Agent.

DD_JMXFETCH_INITIAL_REFRESH_BEANS_PERIOD

Type: int
JMXFetch: sets the initial beans refresh period passed to JMXFetch (controls how often it refreshes the list of MBeans during the initial phase). If unset, JMXFetch uses its default behavior.

DD_JMXFETCH_METRICS_CONFIGS

Type: string
JMXFetch (deprecated): comma-separated list of additional metric config YAML files to load (passed to JMXFetch as metric config files).

DD_JMXFETCH_MULTIPLE_RUNTIME_SERVICES_ENABLED

Type: boolean
Default: false
JMXFetch/runtime metrics: when enabled, collects service names from entry traces and supplies them to JMXFetch so runtime metrics can be reported for multiple services (up to the configured limit). Default: false.

DD_JMXFETCH_MULTIPLE_RUNTIME_SERVICES_LIMIT

Type: int
Default: 10
JMXFetch/runtime metrics: maximum number of distinct service names to track/report when multiple-runtime-services is enabled. Default: 10.

DD_JMXFETCH_REFRESH_BEANS_PERIOD

Type: int
How often to refresh list of available JMX beans (in seconds).

DD_JMXFETCH_START_DELAY

Type: string
JMXFetch/JMX initialization: delay (in seconds) before starting the JMX subsystem (used by JMXFetch and other features that require JMX). Default: 15.

DD_JMXFETCH_STATSD_HOST

Type: string
Aliases:DD_DOGSTATSD_HOST
Override the address of the trace Agent host that the default tracer attempts to submit DogStatsD metrics to. Use DD_AGENT_HOST to override DD_DOGSTATSD_HOST.

DD_JMXFETCH_STATSD_PORT

Type: int
Aliases:DD_DOGSTATSD_PORT
Overrides the default trace Agent port for DogStatsD metric submission. If the Agent configuration sets dogstatsd_port or DD_DOGSTATSD_PORT to something other than the default 8125, then the library configuration DD_DOGSTATSD_PORT must match it.

DD_RABBIT_INCLUDE_ROUTINGKEY_IN_RESOURCE

Type: boolean
Default: true
RabbitMQ AMQP instrumentation: when enabled, includes the routing key in the span resource name for basic.publish (formats as basic.publish <exchange> -> <routingKey>). Default: true.

DD_RABBIT_PROPAGATION_DISABLED_EXCHANGES

Type: string
RabbitMQ AMQP instrumentation: list of exchange names for which trace context propagation should be disabled (no header injection/extraction).

DD_RABBIT_PROPAGATION_DISABLED_QUEUES

Type: string
RabbitMQ AMQP instrumentation: list of queue names for which trace context propagation should be disabled (no header injection/extraction).

DD_TRACE_AKKA_FORK_JOIN_EXECUTOR_TASK_NAME

Type: string
Akka concurrency instrumentation: fully qualified class name of a custom/shaded AkkaForkJoinTask wrapper to instrument for context propagation (used as a configured matching type). Default: empty (use built-in Akka class).

DD_TRACE_AKKA_FORK_JOIN_POOL_NAME

Type: string
Akka concurrency instrumentation: fully qualified class name of a custom/shaded Akka ForkJoinPool to instrument for context propagation (used as a configured matching type). Default: empty (use built-in Akka class).

DD_TRACE_AKKA_FORK_JOIN_TASK_NAME

Type: string
Akka concurrency instrumentation: fully qualified class name of a custom/shaded ForkJoinTask subclass to instrument for context propagation. When set, the instrumentation also matches the configured class in addition to the default Akka ForkJoinTask. Default: empty (use built-in Akka class).

DD_TRACE_AWSADD_SPAN_POINTERS

Type: boolean
Default: true
Aliases:DD_AWSADD_SPAN_POINTERS
AWS: when enabled, adds span pointers (span links) to spans for supported AWS operations (e.g., S3 object and DynamoDB item) so the touched resource can be uniquely identified. Default: true.

DD_TRACE_AXIS_PROMOTE_RESOURCE_NAME

Type: boolean
Default: false
Axis2: when enabled, promotes the SOAP action (or destination address) extracted from Axis2 messages to the local root span resource name for server-side traces. Default: false.

DD_TRACE_AXIS_TRANSPORT_CLASS_NAME

Type: string
Axis2: fully qualified class name of a custom transport sender to instrument. When set, the tracer instruments that transport sender (in addition to known defaults) to create axis2.transport spans and inject propagation headers. Default: empty.

DD_TRACE_EXPERIMENTAL_JDBC_POOL_WAITING_ENABLED

Type: boolean
Default: false
Since: v1.55.0
JDBC connection pool instrumentation: when enabled, creates pool.waiting spans to measure time spent blocked waiting for a connection from the pool (e.g., HikariCP/DBCP2). Spans are only created when blocking is detected. Default: false.

DD_TRACE_EXPERIMENTAL_JEE_SPLIT_BY_DEPLOYMENT

Type: boolean
Default: false
JEE split-by-deployment: when enabled (and the service name is not explicitly set), allows overriding span service names using per-classloader contextual service name, so different deployments (webapps) can be reported as separate services. Default: false.

DD_USM_ENABLED

Type: boolean
Default: false
Universal Service Monitoring (USM): when enabled, activates USM as a target system so USM-specific instrumentations/features can be installed by the Java tracer agent. Default: false.

Configuration Kinds

Each integration can support one or more of these configuration patterns. Replace <INTEGRATION> with the integration name (for example, GRPC, AWS, REDIS).

Per-Integration Settings (525 integrations)

Each section lists all configuration keys available for a specific integration.