Add support for span id remapper in logs pipelines processors

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-02-21 08:02:09.923530",
-            "spec_repo_commit": "8f2d39c3"
+            "regenerated": "2025-02-21 18:18:14.103443",
+            "spec_repo_commit": "5de91bd6"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-02-21 08:02:18.314729",
-            "spec_repo_commit": "8f2d39c3"
+            "regenerated": "2025-02-21 18:18:22.362127",
+            "spec_repo_commit": "5de91bd6"
         }
     }
 }

content/en/api/v1/logs-pipelines/request.CreateLogsPipeline_2707101123.json

@@ -0,0 +1,17 @@
+{
+  "filter": {
+    "query": "source:python"
+  },
+  "name": "testPipeline",
+  "processors": [
+    {
+      "type": "span-id-remapper",
+      "is_enabled": true,
+      "name": "test_filter",
+      "sources": [
+        "dd.span_id"
+      ]
+    }
+  ],
+  "tags": []
+}

data/api/v1/CodeExamples.json

@@ -597,6 +597,13 @@
       "description": "Send logs returns \"Response from server (always 200 empty JSON).\" response"
     }
   ],
+  "CreateLogsPipeline": [
+    {
+      "group": "logs_pipelines",
+      "suffix": "_2707101123",
+      "description": "Create a pipeline with Span Id Remapper returns \"OK\" response"
+    }
+  ],
   "SubmitDistributionPoints": [
     {
       "group": "metrics",

data/api/v1/full_spec.yaml

@@ -6156,6 +6156,7 @@ components:
       - $ref: '#/components/schemas/LogsLookupProcessor'
       - $ref: '#/components/schemas/ReferenceTableLogsLookupProcessor'
       - $ref: '#/components/schemas/LogsTraceRemapper'
+      - $ref: '#/components/schemas/LogsSpanRemapper'
     LogsQueryCompute:
       description: Define computation for a log query.
       properties:
@@ -6267,6 +6268,43 @@ components:
       x-enum-varnames:
       - TIME_ASCENDING
       - TIME_DESCENDING
+    LogsSpanRemapper:
+      description: "There are two ways to define correlation between application spans
+        and logs:\n\n  1. Follow the documentation on [how to inject a span ID in
+        the application logs](https://docs.datadoghq.com/tracing/connect_logs_and_traces).\n
+        \ Log integrations automatically handle all remaining setup steps by default.\n\n
+        \ 2. Use the span remapper processor to define a log attribute as its associated
+        span ID."
+      properties:
+        is_enabled:
+          default: false
+          description: Whether or not the processor is enabled.
+          type: boolean
+        name:
+          description: Name of the processor.
+          type: string
+        sources:
+          default:
+          - dd.span_id
+          description: Array of source attributes.
+          items:
+            description: Attribute to extract the span ID from.
+            type: string
+          type: array
+        type:
+          $ref: '#/components/schemas/LogsSpanRemapperType'
+      required:
+      - type
+      type: object
+    LogsSpanRemapperType:
+      default: span-id-remapper
+      description: Type of logs span remapper.
+      enum:
+      - span-id-remapper
+      example: span-id-remapper
+      type: string
+      x-enum-varnames:
+      - SPAN_ID_REMAPPER
     LogsStatusRemapper:
       description: "Use this Processor if you want to assign some attributes as the
         official status.\n\nEach incoming status value is mapped as follows.\n\n  -
@@ -6382,7 +6420,7 @@ components:
           - dd.trace_id
           description: Array of source attributes.
           items:
-            description: Attribute to extract the Trace ID from.
+            description: Attribute to extract the trace ID from.
             type: string
           type: array
         type: