New component: Datadog Semantic Processor

The purpose and use-cases of the new component

Currently the way in which OpenTelemetry semantics are mapped to those in Datadog is documented, but it is hard to observe the output of this mapping before it is shipped to Datadog since it is executed by the datadogexporter. This is problematic because users are often confused by the logic or wish to override it.

Rather than silently mapping over OpenTelemetry semantics to Datadog semantics in our datadogexporter we will provide a datadogsemanticsprocessor that performs the same mapping explicitly within the context of OpenTelemetry signals and namespaces the result under datadog.

This work will also involve modifying datadogexporter to expect signals in the new format.

Example configuration for the component

receivers:
  otlp:
    protocols:
      http:
      grpc:
processors:
  datadogsemantics:
exporters:
  debug:
  datadog:
        # ...

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [datadogsemantics]
      exporters: [datadog]
    traces/debug:
      receivers: [otlp]
      processors: [datadogsemantics]
      exporters: [debug]

Telemetry data types supported

Traces, metrics, and logs

Is this a vendor-specific component?

[X] This is a vendor-specific component
[ ] If this is a vendor-specific component, I am a member of the OpenTelemetry organization.
[X] If this is a vendor-specific component, I am proposing to contribute and support it as a representative of the vendor.

Code Owner(s)

@IbraheemA

Sponsor (optional)

@songy23

Additional context

No response

open-telemetry / opentelemetry-collector-contrib