Write to the run log
PUT/dataset-run-log/:datasetRunId
Appends a line to the run log, with the level and an optional context. Proton shows the log as Markdown, filters it by level and highlights warnings and errors, and log search finds the line across runs.
- The line goes to the step that was open when it arrived.
- Without
level, the line is Info. An unknown level also becomes Info. - The message can be up to 8 KB (above that it is cut), and the context, a JSON object, up to 4 KB (above that, only the beginning is kept).
- Each run keeps up to 10 thousand lines. The first one beyond that becomes a Proton notice
(
context.code: logTruncated), and the following ones are not added: the full log stays in the run's log file, which the runner uploads.
The running text of the log (log, in GET /dataset-run-log) still has the date and time (UTC) in front
of each line, except with disableDateTime, and the level in front of the lines that are not Info
([Alerta], [Erro], [Crítico]). Near 64 KB, it stops growing, and the line stays only in the per-line
log (GET /dataset-run/{id}/log-entries).
The run id goes in the body (idDatasetRun); the path id is not used.
Permission: Runs: update.
Request
Responses
- 200
- 400
- 401
- 403
- 422
Log updated
idDatasetRun was not sent
Missing, invalid or expired token
The profile of the token user does not have the permission for the route
The run does not belong to the organization of the token