TracerSettings property: Exporter.AgentUri Sets the URL endpoint where traces are sent. Overrides DD_AGENT_HOST and DD_TRACE_AGENT_PORT if set. If the Agent configuration sets receiver_port or DD_APM_RECEIVER_PORT to something other than the default 8126, then DD_TRACE_AGENT_PORT or DD_TRACE_AGENT_URL must match it. Note that Unix Domain Sockets (UDS) are not supported on .NET Framework. Default: http://<DD_AGENT_HOST>:<DD_TRACE_AGENT_PORT> if they are set or http://localhost:8126.
TracerSettings property: GlobalSamplingRate Default: Defaults to the rates returned by the Datadog Agent Enables ingestion rate control. This parameter is a float representing the percentage of spans to sample. Valid values are from 0.0 to 1.0.
For more information, see Ingestion Mechanisms.
Set the sample rate to 20%: [{"sample_rate": 0.2}]
Set the sample rate to 10% for services starting with ‘a’ and span name ‘b’ and set the sample rate to 20% for all other services: [{"service": "a.*", "name": "b", "sample_rate": 0.1}, {"sample_rate": 0.2}]
Default: null A JSON array of objects. Rules are applied in configured order to determine the span’s sample rate. The sample_rate value must be between 0.0 and 1.0 (inclusive). For more information, see Ingestion Mechanisms. Example: Set the span sample rate to 50% for the service my-service and operation name http.request, up to 50 traces per second: [{"service": "my-service", "name": "http.request", "sample_rate":0.5, "max_per_second": 50}]
自動インスツルメンテーションオプションコンフィギュレーション
DD_TRACE_HEADER_TAGS
TracerSettings property:HeaderTags Accepts a map of case-insensitive header keys to tag names and automatically applies matching 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> and http.response.headers.<header-name> respectively.
Example (with specified tag names): User-ID:userId If the Request has a header User-ID, its value is applied as tag userId to the spans produced by the service.
Example (without specified tag names): User-ID If the Request has a header User-ID, its value is applied as tag http.request.headers.User-ID. If the Response has a header User-ID, its value is applied as tag http.response.headers.User-ID.
Added in version 1.18.3. Response header support and entries without tag names added in version 1.26.0. Beta: Starting in version 2.35.0, if Agent Remote Configuration is enabled where this service runs, you can set DD_TRACE_HEADER_TAGS in the Service Catalog UI.
DD_TRACE_CLIENT_IP_ENABLED
関連する IP ヘッダーからクライアント IP を収集できるようにします。 バージョン 2.19.0 で追加されました。 デフォルト: false
DD_TRACE_CLIENT_IP_HEADER
The IP header to be used for client IP collection, for example: x-forwarded-for. Added in version 2.19.0. Default: Datadog parses the following: 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. If several are present, none will be reported.
TracerSettings property: TraceEnabled Enables or disables all instrumentation. Valid values are: true or false. Default: trueNote: Setting the environment variable to false completely disables the client library, and it cannot be enabled through other configuration methods. If it is set to false through another configuration method (not an environment variable), the client library is still loaded, but traces will not be generated.
Enables linking between data sent from APM and the Database Monitoring product when set to service or full. The service option enables the connection between DBM and APM services. The full option enables connection between database spans with database query events. Available for Postgres and MySQL. Default: disabled
TracerSettings property: LogsInjectionEnabled Enables or disables automatic injection of correlation identifiers into application logs. Your logger needs to have a source that sets the trace_id mapping correctly. The default source for .NET Applications, csharp, does this automatically. For more information, see correlated logs in the Trace ID panel.
