List of options available to the tracer.
Enable Trace Analytics.
Client token for browser tracing. Can be generated in the UI at
Integrations -> APIs.
Enable debug logging in the tracer.
Options specific for the Dogstatsd agent.
The port of the Dogstatsd agent that the metrics will submitted to.
Whether to enable the tracer.
Set an application’s environment e.g. prod, pre-prod, stage.
Experimental features can be enabled all at once by using true or individually using key / value pairs.
Interval in milliseconds at which the tracer will submit traces to the agent.
The address of the trace agent that the tracer will submit to.
Whether to enable trace ID injection in log records to be able to correlate traces with logs.
A string representing the minimum tracer log level to use when debug logging is enabled
Custom logger to be used by the tracer (if debug = true), should support debug() and error() methods see https://datadog.github.io/dd-trace-js/#custom-logging
Whether to load all built-in plugins.
The port of the trace agent that the tracer will submit to.
Whether to report the hostname of the service host. This is used when the agent is deployed on a different host and cannot determine the hostname automatically.
Whether to enable runtime metrics.
Percentage of spans to sample as a float between 0 and 1.
Specifies which scope implementation to use. The default is to use the best implementation for the runtime. Only change this if you know what you are doing.
The service name to be used for this program. If not set, the service name will attempted to be inferred from package.json
Global tags that should be assigned to every span.
Whether to track the scope of async functions. This is needed for async/await to work with non-native promises (thenables). Only disable this if you are sure only native promises are used with async/await.
The url of the trace agent that the tracer will submit to. Takes priority over hostname and port, if set.
Generated using TypeDoc