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

Tail Logs

POST
/observability/v1/workspaces/{workspace}/engines/{engine}/logs:tail
 
curl --request POST \
  --url https://example.com/observability/v1/workspaces/example/engines/example/logs:tail \
  --header 'Content-Type: application/json' \
  --data '{ "workspace": "example", "engine": "example", "query": "example", "filter": "example" }'

Live-tails matching log lines as a server stream until the client cancels.

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
workspace
required
string

The workspace whose telemetry is tailed. Live tail is single-workspace only: the organisation-wide ’-’ wildcard is rejected (cross-workspace access is read-only).

engine
required
string

The provider: qibdo, aws, gcp, or azure (the wildcard ’-’ is not allowed for tail).

Request Body required

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

TailLogsRequest

Request for TailLogs.

object
workspace
required

The workspace whose telemetry is tailed. Live tail is single-workspace only: the organisation-wide ’-’ wildcard is rejected (cross-workspace access is read-only).

string
engine
required

The provider: qibdo, aws, gcp, or azure (the wildcard ’-’ is not allowed for tail).

string
query
required

The native log query expression (LogQL for the qibdo engine).

string
filter

AIP-160 filter expression.

string
Example generated
{
  "workspace": "example",
  "engine": "example",
  "query": "example",
  "filter": "example"
}

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

Media type application/json

TailLogsResponse

One streamed log line from a live tail.

object
entry

The log line.

object
timestamp

When the line was emitted.

string format: date-time
line

The raw log line.

string
labels

The stream labels (the unique label set this line belongs to).

object
key
additional properties
string
Example generated
{
  "entry": {
    "timestamp": "2026-04-15T12:00:00Z",
    "line": "example",
    "labels": {
      "additionalProperty": "example"
    }
  }
}

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"
    }
  ]
}