Skip to content
qibdo qibdo
v1
API version
  • v1
Theme
Book a demo

Create Log Sink

POST
/observability/v1/workspaces/{workspace}/engines/{engine}/log-sinks
 
curl --request POST \
  --url https://example.com/observability/v1/workspaces/example/engines/example/log-sinks \
  --header 'Content-Type: application/json' \
  --data '{ "location_id": "example", "name": "example", "qibdo": { "destination": { "archive": { "container": "example", "path": "example" }, "stream": { "name": "example" }, "external": { "target": "example", "reference": "example" } }, "inclusion_filter": "example", "exclusion_filter": "example" } }'

Creates a log sink in the workspace on the given provider. A specific provider is required.

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
workspace
required
string

The workspace to create the log sink in.

engine
required
string

The provider: qibdo, aws, gcp, or azure (a specific provider is required for create).

Request Body required

Section titled “Request Body required ”
Media type application/json

A log sink routes a workspace’s matching log lines to a destination (an archive, a downstream stream, or an external endpoint), selecting which lines flow with inclusion/exclusion filters. The provider that operates the sink is reported by the read-only engine field.

object
id

The unique identifier of the log sink.

stringOutput only
workspace_id

The workspace this sink belongs to. Derived from the {workspace} path segment on create; reported read-only thereafter.

stringOutput only
location_id
required

Weak reference to a topology Location — where the telemetry resides. Immutable after create.

string
name
required

The sink’s handle: a DNS-label (lowercase alphanumerics and hyphens, up to 63 characters), unique within the workspace. Set on create, immutable thereafter.

string
engine

The provider that operates this sink.

string format: enum Output only
Allowed values: ENGINE_UNSPECIFIED ENGINE_QIBDO ENGINE_AWS ENGINE_GCP ENGINE_AZURE
created

Timestamp when the sink was created.

string format: date-time Output only
updated

Timestamp when the sink was last updated.

string format: date-time Output only
qibdo

Routing spec for a Qibdo-managed sink.

object
destination
required

Where the matched lines are delivered.

object
archive

Long-term object-archive delivery.

object
container
required

The object container (bucket) that receives the archived lines.

string
path
required

The object-key path prefix under which lines are written.

string
stream

Continuous delivery to a named downstream stream.

object
name
required

The downstream stream name.

string
external

Delivery to an external endpoint.

object
target
required

A free-form descriptor of the external delivery target.

string
reference
required

An opaque reference (endpoint, handle) for the external target.

string
inclusion_filter
required

AIP-160 filter expression selecting which log lines are routed (required).

string
exclusion_filter

Optional AIP-160 filter expression excluding lines from the routed set.

string

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

Media type application/json

ObservabilityOperation

Tracks the synchronous result of an observability config-plane command (retention, sink, or ingestion mutation). Engine-neutral — operations carry no engine axis.

object
id

The unique operation identifier.

stringOutput only
resource_id

The id of the affected resource.

stringOutput only
resource_type

The type of resource the operation acted upon (URN).

stringOutput only
operation_type

The operation type (CREATE, UPDATE, DELETE).

string format: enum Output only
Allowed values: OBSERVABILITY_OPERATION_TYPE_UNSPECIFIED OBSERVABILITY_OPERATION_TYPE_CREATE OBSERVABILITY_OPERATION_TYPE_UPDATE OBSERVABILITY_OPERATION_TYPE_DELETE
status

The operation status (DONE for synchronous config mutations).

string format: enum Output only
Allowed values: OBSERVABILITY_OPERATION_STATUS_UNSPECIFIED OBSERVABILITY_OPERATION_STATUS_PENDING OBSERVABILITY_OPERATION_STATUS_RUNNING OBSERVABILITY_OPERATION_STATUS_DONE OBSERVABILITY_OPERATION_STATUS_ERROR
insert_time

When the operation was recorded.

string format: date-time Output only
start_time

When execution started.

string format: date-time Output only
end_time

When execution completed.

string format: date-time Output only
progress

Progress percentage (0–100).

integer format: int32 Output only
Example 
{
  "operation_type": "OBSERVABILITY_OPERATION_TYPE_UNSPECIFIED",
  "status": "OBSERVABILITY_OPERATION_STATUS_UNSPECIFIED"
}

default

Section titled “default ”

Default error response

Media type application/json

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

object
code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32
message

A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.

string
details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object
@type

The type of the serialized message.

string
key
additional properties
any
Example generated
{
  "code": 1,
  "message": "example",
  "details": [
    {
      "@type": "example"
    }
  ]
}