2.0.0b2 (2026-04-17)
Features Added
- Startup configuration logging —
AgentServerHostlifespan now emits three INFO-level log lines at startup: platform environment (agent name, version, port, session ID, SSE keep-alive), connectivity (project endpoint and OTLP endpoint masked to scheme://host, Application Insights configured flag), and host options (shutdown timeout, registered protocols). Sensitive values (Application Insights connection string) are never logged. InboundRequestLoggingMiddleware— pure-ASGI middleware wired automatically byAgentServerHostthat logs every inbound HTTP request. Logs method, path (no query string), status code, duration in milliseconds, and correlation headers (x-request-id,x-ms-client-request-id). Status codes >= 400 are logged at WARNING; unhandled exceptions are logged as status 500 at WARNING. OpenTelemetry trace ID is included when an active trace exists.- Inbound request logs now include
trace-idextracted from the W3Ctraceparentheader, even when no OTel span is active at middleware level. Previously the trace-id was only available after the endpoint handler created a request span.
Bugs Fixed
- Fixed duplicate console log output when a
StreamHandlerwas already present on the root logger (e.g. fromlogging.basicConfig()or framework setup). The SDK now detects any existingStreamHandlerbefore adding its own, not just its sentinel-marked handler.