Adds OpenTelemetry source support for metrics pipelines (DataDog#3759)

Co-authored-by: ci.datadog-api-spec <packages@datadoghq.com>

Author: api-clients-generation-pipeline[bot]

.generator/schemas/v2/openapi.yaml

@@ -44821,7 +44821,7 @@ components:
         Protocol (OTLP) over gRPC and HTTP.
 
 
-        **Supported pipeline types:** logs'
+        **Supported pipeline types:** logs, metrics'
       properties:
         grpc_address_key:
           description: Environment variable name containing the gRPC server address
@@ -44851,6 +44851,7 @@ components:
       type: object
       x-pipeline-types:
       - logs
+      - metrics
     ObservabilityPipelineOpentelemetrySourceType:
       default: opentelemetry
       description: The source type. The value should always be `opentelemetry`.

api/datadogV2/model_observability_pipeline_opentelemetry_source.go

@@ -12,7 +12,7 @@ import (
 
 // ObservabilityPipelineOpentelemetrySource The `opentelemetry` source receives telemetry data using the OpenTelemetry Protocol (OTLP) over gRPC and HTTP.
 //
-// **Supported pipeline types:** logs
+// **Supported pipeline types:** logs, metrics
 type ObservabilityPipelineOpentelemetrySource struct {
 	// Environment variable name containing the gRPC server address for receiving OTLP data. Must be a valid environment variable name (alphanumeric characters and underscores only).
 	GrpcAddressKey *string `json:"grpc_address_key,omitempty"`

examples/v2/observability-pipelines/ValidatePipeline_884022323.go

@@ -0,0 +1,76 @@
+// Validate a metrics pipeline with opentelemetry source returns "OK" response
+
+package main
+
+import (
+	"context"
+	"encoding/json"
+	"fmt"
+	"os"
+
+	"github.com/DataDog/datadog-api-client-go/v2/api/datadog"
+	"github.com/DataDog/datadog-api-client-go/v2/api/datadogV2"
+)
+
+func main() {
+	body := datadogV2.ObservabilityPipelineSpec{
+		Data: datadogV2.ObservabilityPipelineSpecData{
+			Attributes: datadogV2.ObservabilityPipelineDataAttributes{
+				Config: datadogV2.ObservabilityPipelineConfig{
+					PipelineType: datadogV2.OBSERVABILITYPIPELINECONFIGPIPELINETYPE_METRICS.Ptr(),
+					Destinations: []datadogV2.ObservabilityPipelineConfigDestinationItem{
+						datadogV2.ObservabilityPipelineConfigDestinationItem{
+							ObservabilityPipelineDatadogMetricsDestination: &datadogV2.ObservabilityPipelineDatadogMetricsDestination{
+								Id: "datadog-metrics-destination",
+								Inputs: []string{
+									"my-processor-group",
+								},
+								Type: datadogV2.OBSERVABILITYPIPELINEDATADOGMETRICSDESTINATIONTYPE_DATADOG_METRICS,
+							}},
+					},
+					ProcessorGroups: []datadogV2.ObservabilityPipelineConfigProcessorGroup{
+						{
+							Enabled: true,
+							Id:      "my-processor-group",
+							Include: "*",
+							Inputs: []string{
+								"opentelemetry-source",
+							},
+							Processors: []datadogV2.ObservabilityPipelineConfigProcessorItem{
+								datadogV2.ObservabilityPipelineConfigProcessorItem{
+									ObservabilityPipelineFilterProcessor: &datadogV2.ObservabilityPipelineFilterProcessor{
+										Enabled: true,
+										Id:      "filter-processor",
+										Include: "env:production",
+										Type:    datadogV2.OBSERVABILITYPIPELINEFILTERPROCESSORTYPE_FILTER,
+									}},
+							},
+						},
+					},
+					Sources: []datadogV2.ObservabilityPipelineConfigSourceItem{
+						datadogV2.ObservabilityPipelineConfigSourceItem{
+							ObservabilityPipelineOpentelemetrySource: &datadogV2.ObservabilityPipelineOpentelemetrySource{
+								Id:   "opentelemetry-source",
+								Type: datadogV2.OBSERVABILITYPIPELINEOPENTELEMETRYSOURCETYPE_OPENTELEMETRY,
+							}},
+					},
+				},
+				Name: "Metrics OTel Pipeline",
+			},
+			Type: "pipelines",
+		},
+	}
+	ctx := datadog.NewDefaultContext(context.Background())
+	configuration := datadog.NewConfiguration()
+	apiClient := datadog.NewAPIClient(configuration)
+	api := datadogV2.NewObservabilityPipelinesApi(apiClient)
+	resp, r, err := api.ValidatePipeline(ctx, body)
+
+	if err != nil {
+		fmt.Fprintf(os.Stderr, "Error when calling `ObservabilityPipelinesApi.ValidatePipeline`: %v\n", err)
+		fmt.Fprintf(os.Stderr, "Full HTTP response: %v\n", r)
+	}
+
+	responseContent, _ := json.MarshalIndent(resp, "", "  ")
+	fmt.Fprintf(os.Stdout, "Response from `ObservabilityPipelinesApi.ValidatePipeline`:\n%s\n", responseContent)
+}

tests/scenarios/cassettes/TestScenarios/v2/Feature_Observability_Pipelines/Scenario_Validate_a_metrics_pipeline_with_opentelemetry_source_returns_OK_response.freeze

@@ -0,0 +1 @@
+2026-03-10T16:11:47.487Z

tests/scenarios/cassettes/TestScenarios/v2/Feature_Observability_Pipelines/Scenario_Validate_a_metrics_pipeline_with_opentelemetry_source_returns_OK_response.yaml

@@ -0,0 +1,24 @@
+interactions:
+- request:
+    body: |
+      {"data":{"attributes":{"config":{"destinations":[{"id":"datadog-metrics-destination","inputs":["my-processor-group"],"type":"datadog_metrics"}],"pipeline_type":"metrics","processor_groups":[{"enabled":true,"id":"my-processor-group","include":"*","inputs":["opentelemetry-source"],"processors":[{"enabled":true,"id":"filter-processor","include":"env:production","type":"filter"}]}],"sources":[{"id":"opentelemetry-source","type":"opentelemetry"}]},"name":"Metrics OTel Pipeline"},"type":"pipelines"}}
+    form: {}
+    headers:
+      Accept:
+      - application/json
+      Content-Type:
+      - application/json
+    id: 0
+    method: POST
+    url: https://api.datadoghq.com/api/v2/obs-pipelines/pipelines/validate
+  response:
+    body: '{"errors":[]}
+
+      '
+    code: 200
+    duration: 0ms
+    headers:
+      Content-Type:
+      - application/vnd.api+json
+    status: 200 OK
+version: 2

tests/scenarios/features/v2/observability_pipelines.feature

@@ -149,6 +149,14 @@ Feature: Observability Pipelines
     And the response "data.attributes.config.destinations" has length 1
     And the response "data.attributes.config.destinations[0].id" is equal to "updated-datadog-logs-destination-id"
 
+  @team:DataDog/observability-pipelines
+  Scenario: Validate a metrics pipeline with opentelemetry source returns "OK" response
+    Given new "ValidatePipeline" request
+    And body with value {"data": {"attributes": {"config": {"pipeline_type": "metrics", "destinations": [{"id": "datadog-metrics-destination", "inputs": ["my-processor-group"], "type": "datadog_metrics"}], "processor_groups": [{"enabled": true, "id": "my-processor-group", "include": "*", "inputs": ["opentelemetry-source"], "processors": [{"enabled": true, "id": "filter-processor", "include": "env:production", "type": "filter"}]}], "sources": [{"id": "opentelemetry-source", "type": "opentelemetry"}]}, "name": "Metrics OTel Pipeline"}, "type": "pipelines"}}
+    When the request is sent
+    Then the response status is 200 OK
+    And the response "errors" has length 0
+
   @team:DataDog/observability-pipelines
   Scenario: Validate an observability pipeline returns "Bad Request" response
     Given new "ValidatePipeline" request