Stream project logs
Changed onLive-tail project logs as Server-Sent Events. The request body uses the resource selector plus q, start_time, and limit, including runtime logs and function/frontend deployment logs selected with resource.deployments. Deployment logs are not supported for databases. Database logs are a SUPERAGENT feature; resource.type=database from a HOBBY project owner returns 403. The q field uses the same syntax as search and activity requests. Do not send cursor or end_time; use /logs/search for range backfills. Explicit historical start_time values are limited to the plan's retention window (HOBBY: 1 day, SUPERAGENT: 30 days). Resume with Last-Event-ID or the last_event_id query parameter. The cursor is bound to the request body: the resource selector and every filter must match the original request when reconnecting, otherwise the request is rejected with 400.
This is a live tail, not a gap-free backfill. On connect or reconnect the server delivers at most limit of the most recent matching events from the cursor position and then follows new events; events older than that window are not replayed. Use /logs/search to backfill a time range.
Request
- Base URL: https://api.volcano.dev
- URL: https://api.volcano.dev/projects/{id}/logs/stream
- Auth: one of:
- HTTP bearer
- HTTP bearer
Path parameters
Project ID
Query parameters
Opaque stream cursor fallback when setting Last-Event-ID is not practical.
Headers
Opaque stream cursor from the most recent SSE id field.
Request body
Response
Server-Sent Events stream. log events contain a JSON LogSearchEvent; warning events contain a JSON object with an error field.
Changes
- ○
the endpoint scheme security
ProjectAccessTokenwas added to the API - ○
added the new optional request property
/////
- ○
- ▲
added the new path request parameter
id - ▲
added the new required request property
- ▲
the request's body type changed from no type to
object - ▲
the response's body type changed from no type to
objectfor status - ▲
the response's body type changed from no type to
objectfor status - ▲
the response's body type changed from no type to
objectfor status - ▲
the response's body type changed from no type to
objectfor status - ▲
the response's body type changed from no type to
objectfor status - ○
added the new optional request property
- ○
added the new optional request property
- ○
added the new optional request property
- ○
added the optional property
to the response with the status - ○
added the optional property
to the response with the status - ○
added the optional property
to the response with the status - ○
added the optional property
to the response with the status - ○
added the optional property
to the response with the status - ○
added the required property
to the response with the status - ○
added the required property
to the response with the status - ○
added the required property
to the response with the status - ○
added the required property
to the response with the status - ○
added the required property
to the response with the status
- ▲