New component: Datadog Semantic Processor

[IbraheemA]

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?

• This is a vendor-specific component
• If this is a vendor-specific component, I am a member of the OpenTelemetry organization.
• 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

[dmitryax]

@songy23 will you sponsor this component?

[songy23]

I sponsor!

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[julealgon]

Can someone clarify if this is a breaking change for 0.122.0?

I see the component mentioned in the release notes:

• https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.122.0

But it doesn't state what happens next. Are we required to use this processor when upgrading to 122, or is the exporter going to still support "the old format" for a while?

I need to know this as we are preparing documentation for the 122 upgrade, and we need to know exactly what is the consequence of this change here.

[songy23]

@julealgon it is still under development and is not ready for use. @IbraheemA will post updates (blog / announcement) once it is ready.

[songy23]

Also to clarify: you are not required to use this processor even after it is ready. The old OTel -> DD way will continue to work.