Tracing

Create trace sessions to group related logs across a workflow.

Traces are lightweight sessions for correlated events.

Start a trace

local trace = RoSentry.startTrace("RoundStart", {
    maxEvents = 100,
    expiresIn = 3600,
    tags = {"match", "debug"},
    metadata = {
        map = "Desert",
        queue = "ranked",
    },
})

Limits enforced by SDK:

Max active traces per server: 50
Max events per trace: 500
Max expiration timeout: 7200 seconds

Log into a trace

if trace then
    trace:info("Matchmaking complete", { players = 12 })
    trace:debug("Spawn wave", { wave = 1 })
    trace:warn("Slow subsystem", { ms = 280 })
    trace:error("Unexpected state", { state = "nil" })
    trace:finish("completed")
end

finish(status) accepts: completed, error, or timeout.

Trace lifecycle helpers

RoSentry.getTrace(traceId)
RoSentry.endAllTraces("completed")
RoSentry.getActiveTraceCount()

Dashboard traces view

Open /dashboard/traces to filter traces by project and status.

Status values:

active
completed
error
timeout

Capturing Errors and Context

Capture methods, user context, tags, breadcrumbs, and scope isolation.

Dashboard Workflows

Daily incident response flow using overview, errors, traces, and project pages.

On this page

Start a trace Log into a trace Trace lifecycle helpers Dashboard traces view