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

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`.

cassettes/features/v2/observability_pipelines/Validate-a-metrics-pipeline-with-opentelemetry-source-returns-OK-response.frozen

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

cassettes/features/v2/observability_pipelines/Validate-a-metrics-pipeline-with-opentelemetry-source-returns-OK-response.yml

@@ -0,0 +1,50 @@
+# Validate a metrics pipeline with opentelemetry source returns "OK" response
+
+require "datadog_api_client"
+api_instance = DatadogAPIClient::V2::ObservabilityPipelinesAPI.new
+
+body = DatadogAPIClient::V2::ObservabilityPipelineSpec.new({
+  data: DatadogAPIClient::V2::ObservabilityPipelineSpecData.new({
+    attributes: DatadogAPIClient::V2::ObservabilityPipelineDataAttributes.new({
+      config: DatadogAPIClient::V2::ObservabilityPipelineConfig.new({
+        pipeline_type: DatadogAPIClient::V2::ObservabilityPipelineConfigPipelineType::METRICS,
+        destinations: [
+          DatadogAPIClient::V2::ObservabilityPipelineDatadogMetricsDestination.new({
+            id: "datadog-metrics-destination",
+            inputs: [
+              "my-processor-group",
+            ],
+            type: DatadogAPIClient::V2::ObservabilityPipelineDatadogMetricsDestinationType::DATADOG_METRICS,
+          }),
+        ],
+        processor_groups: [
+          DatadogAPIClient::V2::ObservabilityPipelineConfigProcessorGroup.new({
+            enabled: true,
+            id: "my-processor-group",
+            include: "*",
+            inputs: [
+              "opentelemetry-source",
+            ],
+            processors: [
+              DatadogAPIClient::V2::ObservabilityPipelineFilterProcessor.new({
+                enabled: true,
+                id: "filter-processor",
+                include: "env:production",
+                type: DatadogAPIClient::V2::ObservabilityPipelineFilterProcessorType::FILTER,
+              }),
+            ],
+          }),
+        ],
+        sources: [
+          DatadogAPIClient::V2::ObservabilityPipelineOpentelemetrySource.new({
+            id: "opentelemetry-source",
+            type: DatadogAPIClient::V2::ObservabilityPipelineOpentelemetrySourceType::OPENTELEMETRY,
+          }),
+        ],
+      }),
+      name: "Metrics OTel Pipeline",
+    }),
+    type: "pipelines",
+  }),
+})
+p api_instance.validate_pipeline(body)

examples/v2/observability-pipelines/ValidatePipeline_884022323.rb

@@ -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

features/v2/observability_pipelines.feature

@@ -19,7 +19,7 @@
 module DatadogAPIClient::V2
   # The `opentelemetry` source receives telemetry data using the OpenTelemetry Protocol (OTLP) over gRPC and HTTP.
   # 
-  # **Supported pipeline types:** logs
+  # **Supported pipeline types:** logs, metrics
   class ObservabilityPipelineOpentelemetrySource
     include BaseGenericModel