Search log lines across runs of a task
const url = 'http://localhost:9477/api/tasks/example/log/search';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url http://localhost:9477/api/tasks/example/log/searchStreams on disk through the task’s runs newest-first and returns matching lines. Pure on-demand scan; no index is maintained. Use cursor to paginate beyond the per-request hit/run budget.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Task name
Task name
Query Parameters
Section titled “Query Parameters ”Restrict the search to one run (ULID). Empty searches every non-deleted run of the task.
Restrict the search to one run (ULID). Empty searches every non-deleted run of the task.
Substring (or regex when regex=true) to search for
Substring (or regex when regex=true) to search for
Treat q as an RE2 regular expression
Treat q as an RE2 regular expression
Match case-sensitively (default is case-insensitive)
Match case-sensitively (default is case-insensitive)
Max hits returned (default 200)
Max hits returned (default 200)
Opaque continuation token returned by a previous call
Opaque continuation token returned by a previous call
Responses
Section titled “ Responses ”OK
object
A URL to the JSON Schema for this object.
True when no further runs / lines need scanning
Hits ordered newest-run-first, then ascending line within a run
object
Absolute line number within the run
ULID of the run containing this line
Stream identifier (stdout/stderr/system)
Matched line content without trailing newline
Run created_at in Unix milliseconds (used for newest-first sort)
Opaque token to fetch the next page; empty when the scan is exhausted
Number of runs visited by this request
Example
{ "$schema": "http://localhost:9477/schemas/LogSearchBody.json"}default
Section titled “default ”Error
object
A URL to the JSON Schema for this object.
A human-readable explanation specific to this occurrence of the problem.
Optional list of individual error details
object
Where the error occurred, e.g. ‘body.items[3].tags’ or ‘path.thing-id’
Error message text
The value at the given location
A URI reference that identifies the specific occurrence of the problem.
HTTP status code
A short, human-readable summary of the problem type. This value should not change between occurrences of the error.
A URI reference to human-readable documentation for the error.
Example
{ "$schema": "http://localhost:9477/schemas/ErrorModel.json", "detail": "Property foo is required but is missing.", "instance": "https://example.com/error-log/abc123", "status": 400, "title": "Bad Request", "type": "about:blank"}