OPopenobserve
Pipelines

Create new pipeline

Creates a new data processing pipeline with specified transformations and routing rules. Pipelines define how incoming data is processed before storage

post/api/{org_id}/pipelines

Request

Path parameters

org_idstring required

Organization name

Request body

descriptionstring
enabledboolean
kind'user' | 'evaluation'

Distinguishes user-created pipelines from system-managed evaluation pipelines.

  • User pipelines are visible in the Pipeline UI and subject to the "one realtime pipeline per stream" constraint.
  • Evaluation pipelines are hidden from the Pipeline UI, managed exclusively by the Online Eval subsystem, and any number can coexist with a user pipeline on the same stream.
namestring required
orgstring
pipeline_idstring
versioninteger

Example request

{
  "edges": [
    {
      "id": "einput-1-func-1"
    }
  ],
  "nodes": [
    {
      "io_type": "input"
    }
  ]
}

Response

Success

codeinteger required
error_detailstring nullable
hintstring nullable

One-line guidance on how to fix the error (agent self-correction, D4).

idstring nullable
messagestring required
namestring nullable
suggestionsstring[] nullable

Closest valid alternatives for a mistyped field/function name.

trace_idstring nullable
warningsstring[] nullable

Problems with a request that succeeded anyway. Distinct from hint, which explains a failure: these accompany a 200, and the caller is entitled to have meant it.

Changes

No recorded changes to this operation across all 1 revision of this API.