observability

Structured logging with traceId emits JSON to stdout with contextual fields to enable search and correlation. It enforces traceId usage across components and environments to link events, tool calls, and user actions consistently.

Tracing tool calls with OpenTelemetry-like patterns instruments operations with spans and timing. This measures latency and tracks performance visibility by recording execution timing for events and tool calls across development and production environments.

Observability guardrails redact secrets and protect PII to ensure consistent governance across components. This prevents sensitive data from leaking into structured logs, traces, and metrics while maintaining performance visibility.

Yes, observability instrumentation applies across development and production environments. It ensures consistent logging, tracing, and metrics collection for events, tool calls, and user actions regardless of the deployment context.

End-to-end observability is enabled by instrumenting applications with structured logs, traces, and metrics. This approach enforces traceId usage, redacts secrets, and adheres to OpenTelemetry-like patterns for spans and timing to capture events and user actions.