Add the OTel Logback appender (opentelemetry-logback-appender) or Python LoggingHandler to the project dependencies
Configure the appender in logback.xml or via logging.basicConfig / addHandler to route log records into the OTel LoggerProvider
Ensure the LoggerProvider is configured with an OTLP LogRecord exporter pointing at the Collector or backend OTLP endpoint
Verify that trace context (trace_id, span_id) is automatically injected into log records when a span is active on the thread
Set log record severity mappings to align framework log levels (INFO, WARN, ERROR) with OTel SeverityNumber values
Known gotchas
The Logs Bridge API does not replace existing log framework configuration; it adds a bridge appender alongside existing file/console appenders, potentially doubling output
If the SDK is not initialized before the logging framework, early log records emitted during startup are silently lost
Trace context injection only works when a span is active on the current thread or async context; logs emitted outside of a span have empty trace IDs
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp