Ensures that the pipeline with the provided ID is created or modified. The full pipeline needs to be provided to ensure (either update or create) the pipeline. Non present data will only be filled with defaults or left empty, but not take previous values into consideration.
To ensure that the pipeline with the provided ID is created or modified, perform PUT request.
The following is a sample request. Remember to replace the {pipelineID} with a valid ID of the specific pipeline you want to create or update.
Below is the list of mandatory path parameters for updating a Monitoring Pipeline:
| Path Parameters | Type | Description | Example |
|---|---|---|---|
Below is the list of mandatory body parameters for updating a Monitoring Pipeline:
| Body Parameters | Required | Type | Description | Example |
|---|---|---|---|---|
To make authenticated requests to the API, the following fields are mandatory in the request header:
| Header Parameters | Required | Type | Description |
|---|---|---|---|
The following is a sample response. The values returned by each response differ based on the request.
200 Successful operation
Result: The Monitoring Pipeline is successfully updated or created.
pipelineId
string
The ID (UUID) of the Pipeline.
f72521ba-1590-5998-bf96-6eb997a5887d
metadata
no
object
Metadata
{}
properties
yes
object
A pipeline consists of the generic rules and configurations of a monitoring pipeline instance.
{ "name": "Updated Pipeline" }
Authorization
yes
string
The Bearer token enables requests to authenticate using a JSON Web Token (JWT). The token can be generated using the Authentication API.
Content-Type
yes
string
Set this to application/json.