rtClient.errorLogs
SDK methods for reporting a client-side error into the protocol, and for reading the log back.
rtClient.errorLogs is two surfaces in one service: report is for your app, and the rest is
for an operator reading what came in.
rtClient.errorLogs.report(error, context?)
The one most apps want. Takes a string or an Error and an optional context object, returns
ApiResponse<ErrorLog>.
try {
await collect(edition);
} catch (err) {
await rtClient.errorLogs.report(err, { productId, step: "collect" });
}This is not a replacement for your own error tracking - it puts a failure where the protocol operators can see it, which matters for the paths that cross the seam between your app and the protocol.
rtClient.errorLogs.create(input)
The explicit form, when you are constructing the row rather than handing over a caught error.
Reading the log
list(params?) returns PaginatedResponse<ErrorLog>; get(id) fetches one;
updateStatus(id, status) sets an ErrorLogStatus. Operator surface - a product UI has no reason
to render other people's errors.