Remove span_name_as_resource_name and span_name_remappings from your Datadog exporter and connector configurations:

# Remove the highlighted lines if they exist in your configuration
exporters:
  datadog:
    traces:
      span_name_as_resource_name: true
      span_name_remappings:
        "old_name1": "new_name"

connectors:
  datadog/connector:
    traces:
      span_name_as_resource_name: true

1. Remove span_name_as_resource_name and span_name_remappings from your Agent’s OTLP ingest configuration (otlp_config in datadog.yaml):

# Remove the highlighted lines if they exist in your configuration
otlp_config:
  traces:
    span_name_as_resource_name: true
    span_name_remappings:
      "old_name1": "new_name"

2. Remove these environment variables if previously set for the Agent:
   • DD_OTLP_CONFIG_TRACES_SPAN_NAME_AS_RESOURCE_NAME
   • DD_OTLP_CONFIG_TRACES_SPAN_NAME_REMAPPINGS

Launch the OpenTelemetry Collector with the feature gate (requires Collector v0.98.0+):

otelcol --config=config.yaml --feature-gates=datadog.EnableOperationAndResourceNameV2

Enable the feature for OTLP ingest using one of these methods:

• Add the feature flag to your Agent configuration (datadog.yaml):

  # datadog.yaml
  apm_config:
    features: ["enable_operation_and_resource_name_logic_v2"]
  

• Set the environment variable for the Agent process:

  export DD_APM_FEATURES="enable_operation_and_resource_name_logic_v2"
  

  Note: If appending to existing features, use a comma-separated list, for example: export DD_APM_FEATURES="existing_feature:true,enable_operation_and_resource_name_logic_v2"

Launch the OpenTelemetry Collector with the feature gate explicitly disabled using a minus sign (-):

otelcol --config=config.yaml --feature-gates=-datadog.EnableOperationAndResourceNameV2

Disable the feature for OTLP ingest using one of these methods:

• Add the disable flag to your Agent configuration (datadog.yaml):

  # datadog.yaml
  apm_config:
    features: ["disable_operation_and_resource_name_logic_v2"]
  

• Set the environment variable for the Agent process:

  export DD_APM_FEATURES="disable_operation_and_resource_name_logic_v2"
  

  Note: If you already have features configured with this variable, use a comma-separated list, ensuring you disable the correct flag:

  export DD_APM_FEATURES="existing_feature:true,disable_operation_and_resource_name_logic_v2"
  

Since DDOT enables this logic by default, you may need to disable it:

Helm

Pass the feature gate flag to the embedded DDOT Collector using Helm values:

helm upgrade -i <RELEASE_NAME> datadog/datadog \
  -f datadog-values.yaml \
  --set datadog.otelCollector.featureGates="-datadog.EnableOperationAndResourceNameV2"

Datadog Operator

If you are using Datadog Operator, use the DD_APM_FEATURES environment variable override in datadog-agent.yaml:

# datadog-agent.yaml
apiVersion: datadoghq.com/v2alpha1
kind: DatadogAgent
metadata:
  name: datadog
spec:
  override:
    nodeAgent: # Or clusterAgent depending on where DDOT runs
      env:
        - name: DD_APM_FEATURES
          value: "disable_operation_and_resource_name_logic_v2" # Add comma-separated existing features if needed

Use processors in your Collector pipeline:

• To replicate span_name_as_resource_name: Use a transform processor to explicitly set operation.name from the span name. This is generally not recommended as it overrides the improved standard logic, but can be used if specific span names are required as operation names.

  processors:
    transform:
      trace_statements:
        - context: span
          statements:
          - set(attributes["operation.name"], name)
  

• To replicate span_name_remappings: Use a transform processor to conditionally set operation.name. This allows targeted overrides while letting the default logic handle other cases.

  processors:
    transform:
      trace_statements:
        - context: span
          statements:
          # Example: Rename spans named "old_name" to "new_name"
          - set(attributes["operation.name"], "new_name") where name == "old_name"
          # Add more specific renaming rules as needed
  

To replicate span_name_as_resource_name or span_name_remappings, set the operation.name span attribute directly within your instrumented application code before the span is exported. This gives you the most control if you need specific overrides. Consult the OpenTelemetry SDK documentation for your language on how to modify span attributes.