Logging
Structured log lines with levels and context, attached to the session that wrote them.
Send structured log lines — level, message, source, context — and read them in
the console next to the events, errors and replay of the same session. Server
SDKs can forward the logging you already do (Monolog, Python logging,
ILogger) without changing a call site.
Levels
trace · debug · info · warn · error · fatal. Framework level names map
automatically (warning → warn, critical/emergency → fatal,
information → info).
Writing logs
final logs = context.nexus.logs;
logs.info('payment started', source: 'checkout');
logs.warn('retrying charge', context: {'attempt': 2});
logs.error('charge failed', source: 'stripe', context: {'code': 'card_declined'});
await logs.flush();No feedback loops
The logging bridges (Python NexusLogHandler, .NET ILogger) ignore the SDK's
own logger and anything written while the SDK is delivering — otherwise an
HTTP client that logs each request would log Nexus' own traffic forever.
Logs inside request journeys
With Telescope installed, log lines written during a request or job also appear on that journey's timeline, and are forwarded to Logs with a link back to the journey.